EODHD APIs for AI agents
EODHD APIs provide financial market data, including historical prices, live quotes, and fundamentals, over REST and WebSocket, used by traders and analysts building market tools. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in EODHD APIs.
Pull a real-time quote
Get a real-time quote for a ticker before including it in a market update.
Check historical end-of-day data
Get end-of-day pricing for a symbol to chart performance over a date range.
Read-only market data lookups
Keep every market data call read-only, since the API only reports prices and never trades.
11 EODHD APIs actions, graded by risk.
Every EODHD APIs action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
11Look things up. Allowed by default.
- eodhd_apis.get_user_infoGet User Info
- eodhd_apis.get_id_mappingGet ID Mapping
- eodhd_apis.list_exchangesList Supported Exchanges
- eodhd_apis.search_instrumentsSearch Instruments
- eodhd_apis.get_eod_yahoo_styleGet EOD Yahoo Style Data
- eodhd_apis.get_real_time_quoteGet Real-Time Quote
- eodhd_apis.get_ust_yield_ratesGet US Treasury Yield Rates
- eodhd_apis.get_macro_indicatorsGet Macro Indicators
- eodhd_apis.get_mutual_funds_dataGet Mutual Funds Data
- eodhd_apis.get_real_time_websocket_forexGet Real-Time FOREX WebSocket Stream
- eodhd_apis.get_real_time_websocket_us_tradeGet Real-time WebSocket US Trades
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
EODHD APIs in three steps.
- 01Your users connect EODHD APIsThey add their EODHD APIs api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls EODHD APIs through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('eodhd_apis', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How EODHD APIs connects.
Users add their EODHD APIs api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same EODHD APIs connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use EODHD APIs from any agent.
EODHD APIs and Arc0, answered.
Can I use EODHD APIs with Claude, ChatGPT or Cursor?
Yes. Connect EODHD APIs to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the EODHD APIs actions you allow.
How do users connect EODHD APIs?
Users add their EODHD APIs api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which EODHD APIs actions can my agent take?
11 in total: 11 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in EODHD APIs?
Yes. Allow read actions and deny writes in the EODHD APIs policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call EODHD APIs too?
Yes. The same EODHD APIs connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug EODHD APIs into your agent.
Your users connect EODHD APIs once, under your brand. Your agent gets 11 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan