> ## Documentation Index
> Fetch the complete documentation index at: https://docs.predexon.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Active trader & fund guide
> The combined Data + Execution flow — find an edge with signals and analytics, then act on it through the Trading API.
You want both: data to find edges, execution to act on them. This guide walks the loop end-to-end — discovery, signal, sizing, execution, monitoring — using a single API key across both Predexon products.
The loop:
```
Discover → Signal → Size → Execute → Monitor
(Data API) (Data API) (you) (Trading API) (WebSocket + Data API)
```
***
## 1. Discover
Find the markets you care about. Three common entry points:
`GET /v2/polymarket/markets?sort=volume`
Trending markets, ranked.
`GET /v2/markets/search?q=...`
Cross-venue search by question text.
`GET /v2/markets`
Predexon's normalized outcome view — one `predexon_id` spans every venue holding it.
For cross-venue arbitrage, [matched pairs](/api-reference/matching/matched-pairs) hands you pre-computed pairs with similarity scores.
***
## 2. Signal
Find a reason to trade. The signals Predexon gives you out of the box:
| Signal | Endpoint | What it tells you |
| ---------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- |
| **Smart-money flow** | [`/v2/polymarket/market/{condition_id}/smart-money`](/api-reference/smart-money/smart-money-market) | Are profitable wallets net buyers or sellers right now? |
| **Smart activity** | [`/v2/polymarket/smart-activity`](/api-reference/smart-money/smart-activity) | Which markets are smart wallets piling into? |
| **Top holders** | [`/v2/polymarket/markets/{condition_id}/top-holders`](/api-reference/analytics/top-holders) | Position concentration on each side. |
| **Wallet P\&L** | [`/v2/polymarket/wallet/pnl/{wallet}`](/api-reference/wallet/pnl) | Track-record check before following a wallet. |
| **Cross-venue spread** | [matched pairs](/api-reference/matching/matched-pairs) + [market price](/api-reference/markets/market-price) | Same outcome, different prices — direct arbitrage. |
| **Pending trades** | [WebSocket pending-trades](/websocket/pending-trades) | 3–5s edge on confirmed fills, from the Polygon mempool. |
For a live edge, subscribe to the WebSocket and react in code. For historical edges, pull from REST and backtest — see the [Backtesting section](/data-signals/backtesting/orderbook-replay) for orderbook replay and signal validation.
***
## 3. Size
Sizing decisions are yours. The data you'll usually want before pulling the trigger:
* **Liquidity check**: current [orderbook snapshot](/websocket/orderbook) — what depth is there at your target price?
* **Recent volume**: [volume chart](/api-reference/markets/volume-chart) — is this a thin market or a deep one?
* **Open interest**: [`/v2/polymarket/markets/{condition_id}/open_interest`](/api-reference/markets/open-interest) — total dollars at risk.
* **Your account balance**: [Get Balance](/trading-api/accounts/get-balance) on the venue you're about to trade.
***
## 4. Execute
Execution goes through venue-specific orders.
Place directly on a venue with a `market` bag. Choose your venue, use native order types, and get a normalized response shape.
Either way, you need an account with funded venues — covered in [Trading Quickstart](/trading-api/quickstart). One account spans every venue you trade on.
```python theme={null}
order = requests.post(
f"{BASE}/api/accounts/{account_id}/orders",
headers=HEADERS,
json={
"venue": "polymarket",
"market": {"tokenId": token_id},
"side": "buy",
"type": "limit",
"size": "10",
"price": "0.50",
},
).json()
```
***
## 5. Monitor
Once you have positions, you watch two things: **fills** and **mark-to-market**.
| What | Where |
| ---------------------------------- | ----------------------------------------------------------------------------------- |
| Live fills on your wallet | [WebSocket trades](/websocket/trades) with `filters.users: [""]` |
| Live splits / merges / redemptions | [WebSocket activity](/websocket/activity) |
| Live orderbook + best bid/ask | [WebSocket orderbook](/websocket/orderbook) |
| Current positions (aggregated) | [Get Positions](/trading-api/accounts/get-positions) on the Trading API |
| Realized + unrealized P\&L | [Wallet P\&L](/api-reference/wallet/pnl) on the Data API |
The Data API and Trading API share the same wallet addresses, so your venue wallet from `GET /accounts/{accountId}` plugs straight into any Data API wallet endpoint.
***
## Putting it together
Strategies people build with this loop:
* **Cross-venue arbitrage** — matched pairs + market price to surface spreads; place each leg with a venue-specific order.
* **Smart-money following** — smart-money endpoint or top-holders for entry signals, WebSocket trades to monitor the wallets you're shadowing.
* **Mempool front-running** — pending-trades WebSocket as a leading indicator, venue-specific order with aggressive price.
* **Market-making** — orderbook WebSocket for live depth, venue-specific limit orders, fee-policy partner cuts on any fills you take in.
***
## Next
Full map of the data side — every endpoint, organized by utility.
Full map of the execution side — accounts, funding, fees.