Polymarket US logo
ConnectorPolymarket US

Polymarket US integration for Claude and Codex

Create a Polymarket US connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Polymarket US from Claude

Add the Polymarket US connection to a Space that runs Claude, then use it from every channel in that Space.

Use Polymarket US from Codex

Add the Polymarket US connection to a Space that runs Codex, then use it from every channel in that Space.

Use Polymarket US from Sidekick

Connect your own OpenClaw to Sidekick while Type provides the conversations, permissions, connections, skills, and automations.

Commerce & Payments

What the Polymarket US connector can do

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.

One connection, many Spaces

Connect Polymarket US once, then decide which Spaces can use it in threads, skills, automations, and coding work.

Representative actions

  • 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 executed fills and positions remain, so verify open orders afterward when confirmation matters.

  • 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-order follow-up reads to verify final state.

  • 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 remain; confirm order state afterward when precision matters.

  • 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 for market, liquidity, risk, or funding checks; inspect the returned order state before confirming the position is closed.

  • 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 across multiple markets; read per-order statuses because a batch can contain accepted, filled, and rejected orders.

Connection

API and auth details

Polymarket US provides CFTC-compliant API access for verified US participants and technology partners. Integrations can access trading, account management, market data, funding, orders, reports, positions, reference data, and WebSocket streams with short-lived bearer tokens and participant headers.

FAQ

Questions people ask before connecting Polymarket US

Can Claude use Polymarket US?

Yes. Add a Polymarket US connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with Polymarket US through Type?

Yes. Add a Polymarket US connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a Polymarket US MCP server?

Not exactly. Type uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More commerce & payments connectors