Polymarket US
Polymarket US only. This toolkit connects to the CFTC-compliant Polymarket US product for United States users, not the global Polymarket app. API credentials are created at https://polymarket.us/developers after Polymarket US account verification.
Verdict
Common use cases
- Preview order impact before committing funds
- Close positions when markets resolve early
- Batch-cancel open orders across multiple markets
- Check portfolio activity and recent trades
- Monitor account balances and buying power
Integration
- Vendor
- Polymarket US
- Category
- other
- Auth
- API_KEY
- Tools
- 44
- Composio slug
polymarket_us
Tools
- Cancel All Open Orders
Cancel all authenticated Polymarket US open orders, optionally scoped to specific market slugs. This is broad and destructive for remaining open quantities; omit slugs only when the user clearly asks to cancel every open order. Already exec
- Cancel Multiple Orders
Cancel up to 20 Polymarket US open orders in one request. Use only when the user explicitly asks to cancel the batch. Cancellation removes remaining open quantity but does not undo fills or positions, and batch responses can require per-ord
- Cancel Order
Cancel one Polymarket US open order by exchange-assigned order ID. This is a destructive mutation of the remaining open quantity and should only be used when the user explicitly asks to cancel. Already executed fills and resulting positions
- Close Position Order
Create a live Polymarket US order intended to close an existing position in one market. Use only when the user explicitly asks to close that position. This can trade immediately, leave residual exposure if not fully filled, or be rejected f
- Create Multiple Orders
Submit up to 20 live Polymarket US orders in one request. Use only after the user explicitly asks to place the batch and, when practical, after previewing the same orders. This mutating action can consume buying power and create exposure ac
- Create Order
Submit one live Polymarket US order. Use Preview Order first unless the user has already reviewed the exact order details. This mutating action can reserve buying power, fill immediately, or create real market exposure; the API may also rej
- Get Account Balances
Get the authenticated user's Polymarket US account balances. Use this read-only action to inspect buying power, balances, pending credits, and funds reserved by open orders before previewing or placing orders. Requires Polymarket US signed
- Get Activities
Get authenticated Polymarket US portfolio activities such as trades, resolutions, deposits, withdrawals, referral bonuses, and transfers. Requires Polymarket US signed authentication and returns activity only for that account. Use type filt
- Get Event By ID
Get one Polymarket US event by numeric ID from the public gateway API. Use this after discovery when the caller already has the integer event ID and needs full event details or associated market references. Do not pass slugs here; use Get E
- Get Event By Slug
Get one Polymarket US event by slug from the public gateway API. Use this after search/list discovery or when parsing a Polymarket event URL. Do not pass numeric IDs here; use Get Event By ID for integer IDs. This read-only action does not
- Get League By Slug
Get a current Polymarket US v2 league by slug. Use List Leagues or Get Sport By Slug first if the slug is unknown. This is useful for confirming league metadata before listing events for a league such as "nba" or "nfl". This action does not
- Get Market BBO
Get the best bid and offer for one Polymarket US market by slug. Use this lightweight top-of-book read before quoting, previewing, or explaining an order. If the agent needs depth or slippage context, use Get Market Book instead. The respon
- Get Market Book
Get the public order book for one Polymarket US market by slug. Use this before quoting, previewing, or explaining an order when the agent needs depth beyond the top of book. The response is market data, not an order placement or order prev
- Get Market By ID
Get one Polymarket US market by numeric ID from the public gateway API. Use this after market discovery when the caller already has the integer market ID and needs full market metadata. Do not pass slugs here; use Get Market By Slug for slu
- Get Market By Slug
Get one Polymarket US market by slug from the public gateway API. Use this after search/list discovery or when parsing a Polymarket market URL. Do not pass numeric IDs here; use Get Market By ID for integer IDs. For current pricing before q
- Get Market Settlement
Get settlement information for one Polymarket US market by slug. Use this only for resolved, closed, or historical market workflows where the caller needs public resolution or settlement details. It is not useful for discovering current mar
- Get Markets For Subject
Discover Polymarket US markets associated with a subject ID. Use this action after List Subjects or Get Subject By ID identifies the team, person, candidate, player, nominee, or other entity the user cares about. This is a market discovery
- Get Markets For Subject By Slug
Discover Polymarket US markets associated with a subject slug. Use this action after List Subjects, Get Subject By Slug, or a Polymarket URL identifies the team, person, candidate, player, nominee, or other entity the user cares about. This
- Get Open Orders
Get all open orders for the authenticated Polymarket US user. Use this read-only action before modifying or canceling orders, or to inspect live order exposure. Requires signed authentication, supports optional market slug filters, and does
- Get Order
Get an authenticated user's Polymarket US order by exchange-assigned order ID. Requires signed authentication and returns order details available to that account. Use this read-only action to inspect order state after creating, modifying, o
- Get Series By ID
Get a Polymarket US series by numeric ID. Series are recurring or grouped event collections. Use this action when an agent has a series ID and needs the slug, active status, recurrence, or other public metadata before fetching related event
- Get Sport By Slug
Get a current Polymarket US v2 sport by slug. Use List Sports first if the slug is unknown. The response includes the sport metadata and leagues attached to that sport, which helps agents move from broad sport browsing to league-specific ev
- Get Subject By ID
Get a Polymarket US subject entity by numeric ID. Subjects represent teams, people, candidates, players, nominees, and other named entities attached to markets. Use this action when an agent already has a subject ID and needs its slug, type
- Get Subject By Slug
Get a Polymarket US subject entity by slug. Subjects represent teams, people, candidates, players, nominees, and other named entities attached to markets. Use this action when an agent has a subject slug from a URL or search result and need
- Get Tag By ID
Get a Polymarket US topic, sport, or league tag by numeric ID. Use this action after List Tags or a market/event response returns a tag ID and the agent needs the tag label, slug, hierarchy, or sport/league metadata for filtering or display
- Get Tag By Slug
Get a Polymarket US topic, sport, or league tag by slug. Use this action when an agent has a URL-safe tag slug, such as nba or sports, and needs the tag ID, label, hierarchy, or sport/league metadata for filtering or display. This action do
- Get User Positions
Get the authenticated user's Polymarket US trading positions across all markets or filtered by a specific market slug. Requires Polymarket US signed authentication and only returns positions for that account. Use this read-only action to ve
- List Events
Discover Polymarket US events from the public gateway API. Use this action before event-specific lookups when starting from a topic, category, tag, or broad filter set. Practical guidance for agents: - For currently relevant events, start w
- List Events For League
List Polymarket US events for a current v2 league slug such as "nba" or "nfl". Use List Leagues or Get Sport By Slug first if the slug is unknown. Supports limit/offset pagination, excludeEventId for de-duplicating already-seen events, and
- List Events For Series
List Polymarket US sports events for a legacy v1 series ID. Prefer List Events For Sport or List Events For League for current v2 browsing. Use this action when an agent already has a series ID from a legacy sports workflow and needs relate
- List Events For Sport
List Polymarket US events for a current v2 sport slug such as "football" or "basketball". Use List Sports first if the slug is unknown. Supports limit/offset pagination, excludeEventId for de-duplicating already-seen events, and optional ty
- List Featured Tags
List featured Polymarket US tag sections from the public gateway API. Featured tags are curated browse sections, often with subtags, intended for discovery UI and recommendation flows rather than exhaustive filtering. Use List Tags when the
- List Leagues
List current Polymarket US sports leagues from the v2 public gateway API. This is the preferred action for discovering league slugs such as "nfl" or "nba" before calling Get League By Slug or List Events For League. Supports limit/offset pa
- List Markets
Discover Polymarket US markets from the public gateway API. Use this action when an agent needs candidate market slugs or IDs before reading market details, order books, best bid/offer, or preparing orders. Practical guidance for agents: -
- List Series
List Polymarket US series from the public gateway API. Series are recurring or grouped event collections, such as seasonal or repeated sports event groupings. Use this action to discover a series ID or slug before fetching related events or
- List Sports
List Polymarket US sports from the current v2 public gateway API. Use this for sports browsing and for discovering sport slugs such as "football" or "basketball" before calling Get Sport By Slug or List Events For Sport. This action does no
- List Sports Teams
List Polymarket US sports teams from the legacy v1 public gateway API. Use this action when an agent needs team metadata for sports events or needs to filter teams by league, name, abbreviation, or Polymarket team ID. The Pydantic filter fi
- List Sports Teams For Provider
List Polymarket US legacy v1 sports team mappings for a data provider. Use this action when an agent needs provider-specific team IDs for SportsDataIO or Sportradar integrations. Pass provider as the enum value "PROVIDER_SPORTSDATAIO" or "P
- List Subjects
List Polymarket US subject entities from the public gateway API. Subjects are teams, people, candidates, players, nominees, or other named entities that markets can be about. Use this action to discover the subject ID or slug before calling
- List Tags
List ranked Polymarket US tags from the public gateway API. Tags are topic, sport, league, and browse filters that agents can use to narrow event or market discovery before calling event and market listing tools. Use parentSlug="sports" to
- Modify Multiple Orders
Modify up to 20 Polymarket US open orders in one request. Use only when the user explicitly asks to change the batch. These live cancel-replace style mutations can change funding requirements, exposure, maker-only behavior, queue priority,
- Modify Order
Modify one existing Polymarket US open order. This is a live cancel-replace style mutation and should only be used when the user explicitly asks to change an order. It can alter exposure, required funds, queue priority, and fill behavior; v
- Preview Order
Preview a Polymarket US order without submitting it to the market. Use this signed, read-only action before live order creation to validate parameters and inspect the calculated order response. It requires Polymarket US signed authenticatio
- Search Markets And Events
Search public Polymarket US markets and events for discovery. Use this for natural-language discovery when an agent needs candidate market or event slugs/IDs before calling specific market/event endpoints. Search results should not be treat
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings → Integrations → Browse MCP Servers. 2. Search for 'Polymarket US' and click Connect. 3. You'll be prompted to paste an API key — log into your Polymarket account, visit the API section of your dashboard, and generate a new key with trading permissions. 4. Copy the key and paste it into Switchy's auth modal, then click Save. 5. Switchy will verify the key by fetching your account balances; if successful you'll see a green checkmark. 6. Open any Space, type '@Polymarket US get my account balances' and send — the MCP should return your buying power and reserved funds. 7. If the response arrives, the connection is live and you can preview or place orders by @mentioning Polymarket US in any message.
What teammates see: by default, memories from Polymarket US are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Account Balance
@Polymarket US get my account balances and show me how much buying power I have available right now.Open in a Space →
Preview Market Order
@Polymarket US preview a buy order for 100 shares of 'Yes' in the 2024 election market and tell me the expected fill price.Open in a Space →
Close Open Position
@Polymarket US close my position in the Fed rate decision market by selling all my 'No' shares at the current best price.Open in a Space →
Cancel All Orders
@Polymarket US cancel all my open orders in the Super Bowl winner market so I can reposition at better prices.Open in a Space →
Review Recent Activity
@Polymarket US show me my last ten portfolio activities including any trades that filled in the past hour.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Polymarket US show me my current account balances and any funds tied up in open orders
Your Polymarket US account holds $1,247.32 in available buying power. You have $380.50 reserved across 4 open orders (3 in the 2024 Presidential Election market, 1 in Fed Rate Decision March). Your total balance including reserved funds is $1,627.82. No pending deposits or withdrawals are currently processing.
This read-only example demonstrates balance inspection before placing new orders. Requires API_KEY authentication. The MCP returns real-time account state, but balances fluctuate as orders fill or markets resolve—always check immediately before trading if precision matters.
@Polymarket US place a $50 buy order for YES shares in the 'AI reaches AGI by 2025' market at 0.23 price
Order preview: buying ~217 YES shares at $0.23 would cost $50.00 plus estimated fees of $0.75. Your available buying power of $1,247.32 covers this. If you confirm, the order will post to the book and may fill partially or fully depending on liquidity. Say 'confirm' to submit the live order, or adjust price/size first.
This write example shows order creation, which is destructive—it reserves buying power and can execute immediately against resting liquidity. Always preview orders (via Preview Order tool) before calling Create Order unless the user has already reviewed exact parameters. Partial fills and slippage are common in thinly traded markets.
@Polymarket US summarize my last 10 trades and tell me which markets I'm most exposed to right now
Your last 10 trades span 6 markets. You bought YES in 'Trump wins 2024' (4 trades, net +$320 exposure), sold NO in 'Recession by Q2 2024' (3 trades, net -$180 exposure), and took small positions in Fed rate and tech IPO markets. Currently, your largest open position is $450 in 'Trump wins 2024' YES shares. You've realized $87 in profit from closed positions and hold $620 in unrealized P&L across active markets.
This synthesis example pairs the Get Activities tool (for trade history) with the AI's reasoning to surface portfolio concentration risk. The MCP returns raw activity records; the AI aggregates and interprets them. Note that P&L calculations depend on current market prices, which shift constantly—treat this as a snapshot, not financial advice.
Use-case deep-dives
When live order cancellation matters more than prediction research
A three-person research shop runs a live election-night dashboard tracking 15 state-level markets on Polymarket. As results roll in, they need to cancel stale limit orders and close positions in under 30 seconds—before odds swing 10 points. This MCP wins because it exposes Cancel All Open Orders and Close Position Order with API-key auth, letting the team script rapid exits without clicking through the web UI. The threshold: if you're placing fewer than 5 orders per event, the overhead of API setup outweighs the speed gain. But for shops running 20+ concurrent positions across multiple markets, the batch-cancel and multi-order tools turn manual chaos into a two-line script. If your team trades Polymarket at scale and speed dictates edge, this MCP is the right call.
How Get Activities supports audit trails in prediction trading
A fintech startup allocates a small prediction-market budget for team sentiment tracking—employees can trade on product-launch outcomes or hiring timelines. Finance needs a monthly CSV of all trades, deposits, and resolutions to reconcile the corporate card. This MCP's Get Activities tool pulls authenticated portfolio history in one call, covering trades, withdrawals, referral bonuses, and transfers. The win: no manual export from the Polymarket UI, no copy-paste errors. The trade-off: if your team places fewer than 10 trades per month, a manual export is faster than maintaining API credentials. But once you cross 20 transactions or need programmatic reconciliation for multiple accounts, the MCP saves 15 minutes per close and eliminates transcription risk. If compliance or finance asks for structured activity logs, this tool delivers.
When Create Multiple Orders scales liquidity provision beyond manual entry
A two-person quant team runs a side project providing liquidity on low-volume Polymarket markets—think local elections or niche sports outcomes. They want to post 40 limit orders across 8 markets every morning, adjusting spreads based on overnight news. This MCP's Create Multiple Orders (20 per batch) and Preview Order tools let them script the entire flow: calculate fair odds, preview execution, then submit two batches without touching the web UI. The boundary: if you're posting fewer than 10 orders per day, the manual UI is faster than writing and maintaining the automation. But for teams placing 30+ orders daily or running systematic strategies, the MCP turns a 20-minute morning routine into a 2-minute cron job. If your edge depends on consistent presence across multiple markets, this integration is worth the API-key setup.
Frequently asked
What does the Polymarket US MCP let me do in Switchy?
It connects your Polymarket US account so you can place and cancel prediction-market orders, check balances, close positions, and review trade history—all from Switchy's AI workspace. The MCP exposes 44 tools covering order lifecycle, portfolio activities, and account state. You still need a funded Polymarket US account; Switchy orchestrates the API calls but doesn't hold your funds or execute trades outside Polymarket's infrastructure.
Do I need admin access or special permissions to connect Polymarket US?
You need an API key from your Polymarket US account settings. The key must have trading permissions if you want to place or cancel orders; read-only keys will only support balance and activity queries. Polymarket US doesn't use OAuth, so there's no scope picker—your key either grants full trading access or it doesn't. Store the key in Switchy's credential vault; never paste it into a shared chat.
Can the MCP automatically hedge my positions or set stop-losses?
No. The MCP can create and cancel individual orders or batches when you ask, but it won't monitor markets or trigger conditional logic on its own. If you want automated hedging, you'd need to build that logic in a separate script that calls Switchy's API or use Polymarket's own conditional-order features. The MCP is a request-response tool set, not a background trading bot.
How is this different from using Polymarket's web app or API directly?
The web app is faster for one-off trades and live market browsing. The MCP shines when you want to batch-cancel orders, cross-reference portfolio data with other tools in Switchy, or script repetitive workflows without writing API boilerplate. You're still hitting Polymarket's infrastructure—Switchy just wraps the endpoints in natural-language tools and handles authentication for you.
Who on my team should connect the Polymarket US credential?
Whoever owns the trading account and is comfortable granting Switchy access to place real orders. Because the API key has full trading permissions, treat it like a password—don't share the credential across team members unless you're all trading from the same Polymarket account. Each trader should connect their own key in a private Switchy project if you want separate audit trails.