# How to connect Polymarket to OpenClaw (paste one key, 44 tools) > Connect Polymarket to OpenClaw with ClawLink: paste your Polymarket key once and 44 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/polymarket The usual route to Polymarket access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Polymarket setup: install one ClawHub skill, connect Polymarket in the browser, and OpenClaw can call real Polymarket actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/polymarket ## Setup It takes three steps to connect OpenClaw to Polymarket. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Polymarket** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect polymarket # connect Polymarket (browser OAuth) npx -y @useclawlink/cli actions polymarket # list available actions npx -y @useclawlink/cli run polymarket --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Polymarket in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Polymarket API key once. Verify the connection by asking OpenClaw: > Use Polymarket to us get account balances and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Polymarket is connected in the dashboard, that agent calls the same 44 Polymarket tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Polymarket MCP for OpenClaw Looking for a Polymarket MCP server for OpenClaw? ClawLink connects Polymarket to OpenClaw and exposes 44 Polymarket tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Polymarket integration](https://claw-link.dev/hermes/polymarket) works the same way. ## What the OpenClaw Polymarket integration can do 44 Polymarket tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 44. ### 30 of 44 Polymarket tools for OpenClaw | Tool | What it does | |---|---| | **Us get account balances** `polymarket_us_get_account_balances` | Get the authenticated user's Polymarket US account balances | | **Us get activities** `polymarket_us_get_activities` | Get authenticated Polymarket US portfolio activities such as trades, resolutions, deposits | | **Us get event by ID** `polymarket_us_get_event_by_id` | Get one Polymarket US event by numeric ID from the public gateway API | | **Us get event by slug** `polymarket_us_get_event_by_slug` | Get one Polymarket US event by slug from the public gateway API | | **Us get league by slug** `polymarket_us_get_league_by_slug` | Get a current Polymarket US v2 league by slug | | **Us get market bbo** `polymarket_us_get_market_bbo` | Get the best bid and offer for one Polymarket US market by slug | | **Us get market book** `polymarket_us_get_market_book` | Get the public order book for one Polymarket US market by slug | | **Us get market by ID** `polymarket_us_get_market_by_id` | Get one Polymarket US market by numeric ID from the public gateway API | | **Us get market by slug** `polymarket_us_get_market_by_slug` | Get one Polymarket US market by slug from the public gateway API | | **Us get market settlement** `polymarket_us_get_market_settlement` | Get settlement information for one Polymarket US market by slug | | **Us get markets for subject** `polymarket_us_get_markets_for_subject` | Discover Polymarket US markets associated with a subject ID | | **Us get markets for subject by slug** `polymarket_us_get_markets_for_subject_by_slug` | Discover Polymarket US markets associated with a subject slug | | **Us get open orders** `polymarket_us_get_open_orders` | Get all open orders for the authenticated Polymarket US user | | **Us get order** `polymarket_us_get_order` | Get an authenticated user's Polymarket US order by exchange-assigned order ID | | **Us get series by ID** `polymarket_us_get_series_by_id` | Get a Polymarket US series by numeric ID | | **Us get sport by slug** `polymarket_us_get_sport_by_slug` | Get a current Polymarket US v2 sport by slug | | **Us get subject by ID** `polymarket_us_get_subject_by_id` | Get a Polymarket US subject entity by numeric ID | | **Us get subject by slug** `polymarket_us_get_subject_by_slug` | Get a Polymarket US subject entity by slug | | **Us get tag by ID** `polymarket_us_get_tag_by_id` | Get a Polymarket US topic, sport, or league tag by numeric ID | | **Us get tag by slug** `polymarket_us_get_tag_by_slug` | Get a Polymarket US topic, sport, or league tag by slug | | **Us get user positions** `polymarket_us_get_user_positions` | Get the authenticated user's Polymarket US trading positions across all markets or filtered by | | **Us list events** `polymarket_us_list_events` | Discover Polymarket US events from the public gateway API | | **Us list events for league** `polymarket_us_list_events_for_league` | List Polymarket US events for a current v2 league slug such as "nba" or "nfl" | | **Us list events for series** `polymarket_us_list_events_for_series` | List Polymarket US sports events for a legacy v1 series ID | | **Us list events for sport** `polymarket_us_list_events_for_sport` | List Polymarket US events for a current v2 sport slug such as "football" or "basketball" | | **Us list featured tags** `polymarket_us_list_featured_tags` | List featured Polymarket US tag sections from the public gateway API | | **Us list leagues** `polymarket_us_list_leagues` | List current Polymarket US sports leagues from the v2 public gateway API | | **Us list markets** `polymarket_us_list_markets` | Discover Polymarket US markets from the public gateway API | | **Us list series** `polymarket_us_list_series` | List Polymarket US series from the public gateway API | | **Us list sports** `polymarket_us_list_sports` | List Polymarket US sports from the current v2 public gateway API | ## Example prompts **Us Get Account Balances** > Use Polymarket to us get account balances and walk me through the result in plain English. **Us Get Activities** > Use Polymarket to us get activities and walk me through the result in plain English. **Us Get Event By Id** > Use Polymarket to us get event by id and walk me through the result in plain English. **Us Get Event By Slug** > Use Polymarket to us get event by slug and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Polymarket working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Polymarket API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Polymarket account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Polymarket. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Polymarket actions to the runtime in a format your agent can reliably use. | 44 tools for Polymarket are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Polymarket to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Polymarket in the browser, and the 44 tools above work from chat. There is no SDK and no config file, and the Polymarket key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Polymarket skill but can't call the tools The ClawHub skill teaches OpenClaw about Polymarket, but the calls run through the ClawLink plugin and your connected account. Make sure Polymarket is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Polymarket from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Polymarket tools Polymarket tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Polymarket call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Polymarket returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Polymarket has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Polymarket integration? Yes. ClawLink is the fastest way to connect OpenClaw to Polymarket: link your Polymarket account once in the browser and OpenClaw can call the Polymarket API through 44 ready-made tools — no custom code or token handling. ### How do I add Polymarket to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Polymarket skill from ClawHub, then you click Connect in the dashboard to authorize Polymarket. OpenClaw calls the tools from the next message — no config files, and the Polymarket key you paste is stored server-side instead of in your environment. ### How long does it take to connect Polymarket to OpenClaw? About two minutes. Sign in, click Connect next to Polymarket in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Polymarket up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Polymarket working from chat. ### OpenClaw installed the Polymarket skill but can't call the tools The ClawHub skill teaches OpenClaw about Polymarket, but the calls run through the ClawLink plugin and your connected account. Make sure Polymarket is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related No related integrations yet.