# How to connect EODHD APIs to OpenClaw (paste one key, 11 tools) > Connect EODHD APIs to OpenClaw with ClawLink: paste your EODHD APIs key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/eodhd-apis The usual route to EODHD APIs 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 EODHD APIs setup: install one ClawHub skill, connect EODHD APIs in the browser, and OpenClaw can call real EODHD APIs 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 EODHD APIs. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect EODHD APIs** — 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 eodhd-apis # connect EODHD APIs (browser OAuth) npx -y @useclawlink/cli actions eodhd-apis # list available actions npx -y @useclawlink/cli run eodhd-apis --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 EODHD APIs in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your EODHD APIs API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from EODHD APIs, 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 EODHD APIs is connected in the dashboard, that agent calls the same 11 EODHD APIs 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). ## EODHD APIs MCP for OpenClaw Looking for a EODHD APIs MCP server for OpenClaw? ClawLink connects EODHD APIs to OpenClaw and exposes 11 EODHD APIs 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 EODHD APIs integration](https://claw-link.dev/hermes/eodhd-apis) works the same way. ## What the OpenClaw EODHD APIs integration can do 11 EODHD APIs tools are ready for OpenClaw once the account is connected. ### All 11 EODHD APIs tools for OpenClaw | Tool | What it does | |---|---| | **Get eod yahoo style** `eodhd_apis_get_eod_yahoo_style` | Retrieves end-of-day historical stock price data using Yahoo Finance style parameters via EODHD | | **Get ID mapping** `eodhd_apis_get_id_mapping` | Convert between different security identifiers (CUSIP, ISIN, FIGI, LEI, CIK, ticker symbol) | | **Get macro indicators** `eodhd_apis_get_macro_indicators` | Retrieve macroeconomic indicator data for a specific country from EODHD | | **Get mutual funds data** `eodhd_apis_get_mutual_funds_data` | Retrieves comprehensive fundamental data for mutual funds via EODHD API | | **Get real time quote** `eodhd_apis_get_real_time_quote` | Retrieves real-time (delayed 15-20 minutes for stocks, ~1 minute for forex) OHLCV data for | | **Get real time websocket forex** `eodhd_apis_get_real_time_websocket_forex` | Provides WebSocket connection details for real-time FOREX currency pair data from EODHD | | **Get real time websocket us trade** `eodhd_apis_get_real_time_websocket_us_trade` | Retrieve real-time trade data for the US market via WebSocket | | **Get user info** `eodhd_apis_get_user_info` | Retrieve current user account information and API usage statistics from EODHD | | **Get ust yield rates** `eodhd_apis_get_ust_yield_rates` | Retrieve US Treasury yield curve rates from EODHD API | | **List exchanges** `eodhd_apis_list_exchanges` | Retrieve a list of all supported stock exchanges from EODHD API | | **Search instruments** `eodhd_apis_search_instruments` | Search for stocks, ETFs, mutual funds, bonds, and indices by ticker symbol, company name, or | ## Example prompts **Get Eod Yahoo Style** > Pull the relevant data from EODHD APIs, summarize it in plain English, and point out anything that needs attention. **Get Id Mapping** > Pull the relevant data from EODHD APIs, summarize it in plain English, and point out anything that needs attention. **Get Macro Indicators** > Pull the relevant data from EODHD APIs, summarize it in plain English, and point out anything that needs attention. **Get Mutual Funds Data** > Pull the relevant data from EODHD APIs, 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 EODHD APIs working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the EODHD APIs API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected EODHD APIs 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 EODHD APIs. | 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 EODHD APIs actions to the runtime in a format your agent can reliably use. | 11 tools for EODHD APIs are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes EODHD APIs 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 EODHD APIs in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the EODHD APIs 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 EODHD APIs skill but can't call the tools The ClawHub skill teaches OpenClaw about EODHD APIs, but the calls run through the ClawLink plugin and your connected account. Make sure EODHD APIs 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 EODHD APIs 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 EODHD APIs tools EODHD APIs 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 EODHD APIs 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. ### EODHD APIs 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 EODHD APIs has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw EODHD APIs integration? Yes. ClawLink is the fastest way to connect OpenClaw to EODHD APIs: link your EODHD APIs account once in the browser and OpenClaw can call the EODHD APIs API through 11 ready-made tools — no custom code or token handling. ### How do I add EODHD APIs to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink EODHD APIs skill from ClawHub, then you click Connect in the dashboard to authorize EODHD APIs. OpenClaw calls the tools from the next message — no config files, and the EODHD APIs key you paste is stored server-side instead of in your environment. ### How long does it take to connect EODHD APIs to OpenClaw? About two minutes. Sign in, click Connect next to EODHD APIs in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring EODHD APIs 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 EODHD APIs working from chat. ### OpenClaw installed the EODHD APIs skill but can't call the tools The ClawHub skill teaches OpenClaw about EODHD APIs, but the calls run through the ClawLink plugin and your connected account. Make sure EODHD APIs 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 - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [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.