Venues
The platform values the API and MCP server accept, and what each venue can do. This table is generated from the same registry the API validates against.
A venue is identified everywhere by its platform value. Trader endpoints (list, profile, follow, autopilot) accept only venues whose public tape names the trader; an anonymous venue still appears in the feed, in strategies and in paper autopilot, but has nobody to follow.
Whether a venue is switched on for your account right now is runtime state. Read readiness.liveCopy for that; this page describes what each venue supports, not what is open today.
| platform | Venue | Region | Tape attribution | Trader endpoints | Live autopilot | Quantity unit |
|---|---|---|---|---|---|---|
polymarket | Polymarket | Global | Public wallet | Yes | Manual only (browser wallet) | shares |
polymarket_us | Polymarket US | US | Anonymous tape | No | Your own connected API key | shares |
kalshi | Kalshi | US | Public username | Yes | Your own connected API key | contracts |
hyperliquid | Hyperliquid | Global | Public wallet | Yes | Delegated signer | shares |
novig | Novig | US | Anonymous tape | No | Your own connected API key | contracts |
prophetx | ProphetX | US | Anonymous tape | No | Your own connected API key | contracts |
gemini | Gemini | US | Anonymous tape | No | Your own connected API key | contracts |
Blocker names are scoped by venue
Readiness and copy-log reason codes that belong to one venue carry its platform value as a prefix: kalshi_not_connected, polymarket_us_autopilot_disabled, polymarket_coming_soon. The suffix is stable across venues, so a client can branch on _not_connected or _coming_soon and read the prefix to know which account to fix.