Active trader & fund guide

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:

By volume

GET /v2/polymarket/markets?sort=volumeTrending markets, ranked.

By search

GET /v2/markets/search?q=...Cross-venue search by question text.

By canonical outcome

GET /v2/marketsPredexon’s normalized outcome view — one predexon_id spans every venue holding it.

For cross-venue arbitrage, 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`	Are profitable wallets net buyers or sellers right now?
Smart activity	`/v2/polymarket/smart-activity`	Which markets are smart wallets piling into?
Top holders	`/v2/polymarket/markets/{condition_id}/top-holders`	Position concentration on each side.
Wallet P&L	`/v2/polymarket/wallet/pnl/{wallet}`	Track-record check before following a wallet.
Cross-venue spread	matched pairs + market price	Same outcome, different prices — direct arbitrage.
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 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 — what depth is there at your target price?
Recent volume: volume chart — is this a thin market or a deep one?
Open interest: /v2/polymarket/markets/{condition_id}/open_interest — total dollars at risk.
Your account balance: Get Balance on the venue you’re about to trade.

4. Execute

You have two execution paths.

Unified Order Router

Hand the router a canonical predexonId and let it pick the best venue by price + fees. Best for cross-venue arbitrage and when you don’t care which venue you fill on.

Venue-specific order

Place directly on a venue with a market bag. Best when you have a venue preference, want native order types, or need full control.

Either way, you need an account with funded venues — covered in Trading Quickstart. One account spans every venue you trade on.

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 with `filters.users: ["<your venue wallet>"]`
Live splits / merges / redemptions	WebSocket activity
Live orderbook + best bid/ask	WebSocket orderbook
Current positions (aggregated)	Get Positions on the Trading API
Realized + unrealized P&L	Wallet P&L 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 + router. The router places legs on each venue automatically.
Smart-money following — smart-money endpoint or top-holders for entry signals, router for sizing across venues, 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.

Data & Signals overview

Full map of the data side — every endpoint, organized by utility.

Unified Execution overview

Full map of the execution side — accounts, funding, router, fees.

Documentation Index

​1. Discover

By volume

By search

By canonical outcome

​2. Signal

​3. Size

​4. Execute