# How to connect Polygon.io to OpenClaw (paste one key, 60 tools) > Connect Polygon.io to OpenClaw with ClawLink: paste your Polygon.io key once and 60 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/polygon-io The usual route to Polygon.io 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.io setup: install one ClawHub skill, connect Polygon.io in the browser, and OpenClaw can call real Polygon.io actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Polygon.io. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Polygon.io** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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-io # connect Polygon.io (browser OAuth) npx -y @useclawlink/cli actions polygon-io # list available actions npx -y @useclawlink/cli run polygon-io --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.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Polygon.io API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Polygon.io, 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.io is connected in the dashboard, that agent calls the same 60 Polygon.io 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.io MCP for OpenClaw Looking for a Polygon.io MCP server for OpenClaw? ClawLink connects Polygon.io to OpenClaw and exposes 60 Polygon.io 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.io integration](https://claw-link.dev/hermes/polygon-io) works the same way. ## What the OpenClaw Polygon.io integration can do 60 Polygon.io 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 60. ### 30 of 60 Polygon.io tools for OpenClaw | Tool | What it does | |---|---| | **Get all tickers** `polygon_io_get_all_tickers` | Retrieve a comprehensive list of supported ticker symbols across all asset classes | | **Get condition codes** `polygon_io_get_condition_codes` | Retrieve a unified list of trade and quote condition codes and their definitions | | **Get crypto ema** `polygon_io_get_crypto_ema` | Calculate Exponential Moving Average (EMA) technical indicator for a crypto ticker | | **Get crypto macd** `polygon_io_get_crypto_macd` | Calculate Moving Average Convergence/Divergence (MACD) technical indicator for a crypto ticker | | **Get crypto open close** `polygon_io_get_crypto_open_close` | Get the open, close, high, low, and volume for a cryptocurrency pair on a specific date | | **Get crypto rsi** `polygon_io_get_crypto_rsi` | Calculate the Relative Strength Index (RSI) for a cryptocurrency ticker | | **Get crypto sma** `polygon_io_get_crypto_sma` | Calculate Simple Moving Average (SMA) technical indicator for a cryptocurrency ticker | | **Get daily open close** `polygon_io_get_daily_open_close` | Get the daily open, close, after-hours, and pre-market prices for a stock on a specific date | | **Get dividends** `polygon_io_get_dividends` | Retrieve a historical record of cash dividend distributions for a given ticker | | **Get economy inflation2** `polygon_io_get_economy_inflation2` | Retrieve key indicators of realized inflation including CPI and PCE price indexes with | | **Get ema** `polygon_io_get_ema` | Retrieve the Exponential Moving Average for a stock ticker | | **Get filing** `polygon_io_get_filing` | Retrieve detailed information about a specific SEC filing by filing ID | | **Get filing file** `polygon_io_get_filing_file` | Download a specific file from an SEC filing | | **Get forex ema** `polygon_io_get_forex_ema` | Calculate Exponential Moving Average (EMA) technical indicator for a forex pair | | **Get forex macd** `polygon_io_get_forex_macd` | Calculate Moving Average Convergence/Divergence (MACD) technical indicator for a forex pair | | **Get forex real time currency conversion** `polygon_io_get_forex_real_time_currency_conversion` | Convert amounts between currency pairs using real-time forex rates | | **Get forex rsi** `polygon_io_get_forex_rsi` | Calculate the Relative Strength Index (RSI) technical indicator for a forex pair | | **Get forex sma** `polygon_io_get_forex_sma` | Calculate Simple Moving Average (SMA) technical indicator for a forex pair | | **Get futures quotes** `polygon_io_get_futures_quotes` | Get real-time quote information for futures contracts with bid/ask prices, sizes, and timestamps | | **Get grouped daily** `polygon_io_get_grouped_daily` | Retrieve daily OHLCV data for the entire market for a given date | | **Get historic forex ticks** `polygon_io_get_historic_forex_ticks` | Get historic ticks for a currency pair on a specific date | | **Get inflation expectations** `polygon_io_get_inflation_expectations` | Retrieve inflation expectations data from the Federal Reserve, including market-based rates and | | **Get ipo data** `polygon_io_get_ipo_data` | Retrieve comprehensive information on Initial Public Offerings (IPOs), including upcoming and | | **Get labor market** `polygon_io_get_labor_market` | Retrieve labor market data including unemployment rate, labor force participation rate, average | | **Get macd** `polygon_io_get_macd` | Retrieve the Moving Average Convergence/Divergence (MACD) for a stock ticker | | **Get market holidays** `polygon_io_get_market_holidays` | Retrieve upcoming market holidays and their corresponding open/close times | | **Get market status** `polygon_io_get_market_status` | Retrieve the current trading status across major exchanges and currency markets | | **Get news** `polygon_io_get_news` | Retrieve the most recent news articles for a specified ticker | | **Get options contract overview** `polygon_io_get_options_contract_overview` | Retrieve comprehensive details about a specific options contract including contract type | | **Get options ema** `polygon_io_get_options_ema` | Calculate Exponential Moving Average (EMA) technical indicator for an options ticker | ## Example prompts **Get All Tickers** > Pull the relevant data from Polygon.io, summarize it in plain English, and point out anything that needs attention. **Get Condition Codes** > Pull the relevant data from Polygon.io, summarize it in plain English, and point out anything that needs attention. **Get Crypto Ema** > Pull the relevant data from Polygon.io, summarize it in plain English, and point out anything that needs attention. **Get Crypto Macd** > Pull the relevant data from Polygon.io, 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.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Polygon.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Polygon.io 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.io. | 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.io actions to the runtime in a format your agent can reliably use. | 60 tools for Polygon.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Polygon.io 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.io in the browser, and the 60 tools above work from chat. There is no SDK and no config file, and the Polygon.io 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.io skill but can't call the tools The ClawHub skill teaches OpenClaw about Polygon.io, but the calls run through the ClawLink plugin and your connected account. Make sure Polygon.io 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.io 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.io tools Polygon.io 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.io 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.io 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.io 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.io integration? Yes. ClawLink is the fastest way to connect OpenClaw to Polygon.io: link your Polygon.io account once in the browser and OpenClaw can call the Polygon.io API through 60 ready-made tools — no custom code or token handling. ### How do I add Polygon.io to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Polygon.io skill from ClawHub, then you click Connect in the dashboard to authorize Polygon.io. OpenClaw calls the tools from the next message — no config files, and the Polygon.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect Polygon.io to OpenClaw? About two minutes. Sign in, click Connect next to Polygon.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Polygon.io 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.io working from chat. ### OpenClaw installed the Polygon.io skill but can't call the tools The ClawHub skill teaches OpenClaw about Polygon.io, but the calls run through the ClawLink plugin and your connected account. Make sure Polygon.io 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 - [OpenClaw Metabase integration](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.