# How to connect Polygon to OpenClaw (paste one key, 89 tools) > Connect Polygon to OpenClaw with ClawLink: paste your Polygon key once and 89 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/polygon The usual route to Polygon 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 Polygon setup: install one ClawHub skill, connect Polygon in the browser, and OpenClaw can call real Polygon 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/polygon ## Setup It takes three steps to connect OpenClaw to Polygon. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Polygon** — 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 polygon # connect Polygon (browser OAuth) npx -y @useclawlink/cli actions polygon # list available actions npx -y @useclawlink/cli run polygon --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 Polygon in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Polygon API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Polygon, summarize it in plain English, and point out anything that needs attention. ### 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 Polygon is connected in the dashboard, that agent calls the same 89 Polygon 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). ## Polygon MCP for OpenClaw Looking for a Polygon MCP server for OpenClaw? ClawLink connects Polygon to OpenClaw and exposes 89 Polygon 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 Polygon integration](https://claw-link.dev/hermes/polygon) works the same way. ## What the OpenClaw Polygon integration can do 89 Polygon 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 89. ### 30 of 89 Polygon tools for OpenClaw | Tool | What it does | |---|---| | **Get aggregates** `polygon_get_aggregates` | Fetch custom aggregate OHLCV bars for a stock | | **Get all tickers** `polygon_get_all_tickers` | Retrieve all ticker symbols across asset classes | | **Get condition codes** `polygon_get_condition_codes` | Retrieve a unified list of trade and quote condition codes and their definitions | | **Get crypto aggregates** `polygon_get_crypto_aggregates` | Retrieve aggregate bars for a cryptocurrency over a time range | | **Get crypto all tickers** `polygon_get_crypto_all_tickers` | Retrieve snapshots for all cryptocurrency tickers | | **Get crypto ema** `polygon_get_crypto_ema` | Calculate Exponential Moving Average (EMA) technical indicator for a crypto ticker | | **Get crypto grouped daily** `polygon_get_crypto_grouped_daily` | Retrieve daily grouped bars for all cryptocurrencies on a specified date | | **Get crypto last trade** `polygon_get_crypto_last_trade` | Retrieve the last trade for a specified cryptocurrency pair | | **Get crypto macd** `polygon_get_crypto_macd` | Calculate Moving Average Convergence/Divergence (MACD) technical indicator for a crypto ticker | | **Get crypto open close** `polygon_get_crypto_open_close` | Fetch daily open and close prices for a given crypto pair on a specified date | | **Get crypto prev close** `polygon_get_crypto_prev_close` | Retrieve previous day’s close for a crypto ticker | | **Get crypto rsi** `polygon_get_crypto_rsi` | Calculate the Relative Strength Index (RSI) for a cryptocurrency ticker | | **Get crypto sma** `polygon_get_crypto_sma` | Calculate Simple Moving Average (SMA) technical indicator for a cryptocurrency ticker | | **Get crypto ticker book** `polygon_get_crypto_ticker_book` | Retrieve the full L2 order book for a crypto ticker | | **Get crypto trades** `polygon_get_crypto_trades` | Fetch historical trade data for a cryptocurrency ticker | | **Get dividends** `polygon_get_dividends` | Retrieve dividend data for stocks | | **Get economy inflation** `polygon_get_economy_inflation` | Retrieve key indicators of realized inflation including CPI and PCE price indexes | | **Get ema** `polygon_get_ema` | Retrieve the Exponential Moving Average for a stock ticker | | **Get filing** `polygon_get_filing` | Retrieve SEC filing details by filing ID | | **Get filing file** `polygon_get_filing_file` | Retrieve information about a specific SEC filing file | | **Get forex aggregates** `polygon_get_forex_aggregates` | Retrieve aggregate bars for a forex pair over a date range | | **Get forex ema** `polygon_get_forex_ema` | Calculate Exponential Moving Average (EMA) technical indicator for a forex pair | | **Get forex grouped daily** `polygon_get_forex_grouped_daily` | Retrieve daily grouped OHLC bars for all forex currency pairs on a specified date | | **Get forex historical quotes** `polygon_get_forex_historical_quotes` | Retrieve historical forex quotes for a currency pair over a time range | | **Get forex locales** `polygon_get_forex_locales` | List locales supported by Polygon's forex asset class | | **Get forex macd** `polygon_get_forex_macd` | Calculate Moving Average Convergence/Divergence (MACD) technical indicator for a forex pair | | **Get forex prev close** `polygon_get_forex_prev_close` | Retrieve previous day's close for a forex ticker | | **Get forex real time currency conversion** `polygon_get_forex_real_time_currency_conversion` | Convert amounts between currency pairs using real-time forex rates | | **Get forex rsi** `polygon_get_forex_rsi` | Calculate the Relative Strength Index (RSI) technical indicator for a forex pair | | **Get forex sma** `polygon_get_forex_sma` | Calculate Simple Moving Average (SMA) technical indicator for a forex pair | ## Example prompts **Get Aggregates** > Pull the relevant data from Polygon, summarize it in plain English, and point out anything that needs attention. **Get All Tickers** > Pull the relevant data from Polygon, summarize it in plain English, and point out anything that needs attention. **Get Condition Codes** > Pull the relevant data from Polygon, summarize it in plain English, and point out anything that needs attention. **Get Crypto Aggregates** > Pull the relevant data from Polygon, summarize it in plain English, and point out anything that needs attention. ## 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 Polygon working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Polygon API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Polygon 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 Polygon. | 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 Polygon actions to the runtime in a format your agent can reliably use. | 89 tools for Polygon are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Polygon 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 Polygon in the browser, and the 89 tools above work from chat. There is no SDK and no config file, and the Polygon 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 Polygon skill but can't call the tools The ClawHub skill teaches OpenClaw about Polygon, but the calls run through the ClawLink plugin and your connected account. Make sure Polygon 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 Polygon 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 Polygon tools Polygon 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 Polygon 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. ### Polygon 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 Polygon has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Polygon integration? Yes. ClawLink is the fastest way to connect OpenClaw to Polygon: link your Polygon account once in the browser and OpenClaw can call the Polygon API through 89 ready-made tools — no custom code or token handling. ### How do I add Polygon to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Polygon skill from ClawHub, then you click Connect in the dashboard to authorize Polygon. OpenClaw calls the tools from the next message — no config files, and the Polygon key you paste is stored server-side instead of in your environment. ### How long does it take to connect Polygon to OpenClaw? About two minutes. Sign in, click Connect next to Polygon in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Polygon 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 Polygon working from chat. ### OpenClaw installed the Polygon skill but can't call the tools The ClawHub skill teaches OpenClaw about Polygon, but the calls run through the ClawLink plugin and your connected account. Make sure Polygon 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 - [OpenClaw PostHog integration](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [Connect DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.