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.
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 executed fills and positions remain, so verify open orders afterward when confirmation matters.
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-order follow-up reads to verify final state.
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 remain; confirm order state afterward when precision matters.
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 for market, liquidity, risk, or funding checks; inspect the returned order state before confirming the position is closed.
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 across multiple markets; read per-order statuses because a batch can contain accepted, filled, and rejected orders.
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 reject the order for funding, price, market, or risk checks, so inspect the returned status before confirming placement.
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 authentication and returns only the signed-in account's balances.
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 filters and sortOrder carefully when paging through history.
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 Event By Slug for slugs. This read-only action does not require API key authentication.
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 require API key authentication.
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 require API key authentication.
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 response is market data, not an order placement or order preview. This endpoint requires the market slug, not the numeric market ID, and does not require API key authentication.
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 preview. This endpoint requires the market slug, not the numeric market ID, and does not require API key authentication.
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 slugs. For current pricing before an order, follow with Get Market BBO or Get Market Book. This read-only action does not require API key authentication.
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 quoting, previewing, or placing an order, follow with Get Market BBO or Get Market Book. This read-only action does not require API key authentication.
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 markets or preparing trades on active markets. This endpoint requires the market slug, not the numeric market ID, and does not require API key authentication.
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 tool, not a subject metadata lookup. This action does not require API key authentication.
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 is a market discovery tool, not a subject metadata lookup. This action does not require API key authentication.
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 not place, modify, or cancel orders.
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, or canceling an order.
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 events or markets. This action does not require API key authentication.
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 event discovery. This action does not require API key authentication.
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, or display metadata. This action does not require API key authentication.
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 needs the subject ID or display metadata. This action does not require API key authentication.
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. This action does not require API key authentication.
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 does not require API key authentication.
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 verify API credentials and inspect current exposure.
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 with active=true, closed=false, and archived=false, then paginate with limit and offset. - Pass numeric event IDs in id and event slugs in slug; do not mix the two identifier types. - Events may contain related markets, but use market-specific actions for market details, order books, BBO, settlement, or order preparation. - This read-only discovery action does not require Polymarket API key auth.
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 optional type/section filters. This action does not require API key authentication.
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 related events. Supports limit/offset pagination, excludeEventId for de-duplicating already-seen events, and optional type/section filters. This action does not require API key authentication.
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 type/section filters. This action does not require API key authentication.
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 agent needs the full searchable tag set. This action does not require API key authentication.
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 pagination with a maximum page size of 50. This action does not require API key authentication.
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: - For currently tradable candidates, start with active=true, closed=false, and archived=false, then paginate with limit and offset. - Pass numeric market IDs in id and market slugs in slug; do not mix the two identifier types. - Discovery results are not a substitute for live pricing. Before quoting, previewing, or placing an order, read Get Market BBO for top-of-book or Get Market Book for depth. - This read-only discovery action does not require Polymarket API key auth.
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 markets with series-aware tools. This action does not require API key authentication.
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 not require API key authentication.
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 fields named filters_* are translated to the dotted API query names filters.league, filters.name, filters.abbreviation, and filters.id. This action does not require API key authentication.
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 "PROVIDER_SPORTRADAR"; optionally narrow by Polymarket teamIds and league slug. This action does not require API key authentication.
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 the subject market lookup tools. This action does not require API key authentication.
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 discover sports and league tags. This action does not require API key authentication.
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, and fill risk; the response can be partial, so confirm per-order state after modification when accuracy matters.
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; verify the updated order state after the request when confirmation matters.
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 authentication but does not create, modify, cancel, or reserve funds for an order.
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 treated as live pricing or trading readiness: after selecting a market, read the market details and then Get Market BBO or Get Market Book before quoting, previewing, or placing an order. Use page and limit to paginate. This read-only action does not require API key authentication.