Skip to main content
This is a US-equities finance API with an MCP server in front of it. The routes, tool names, and response shapes match the Financial Datasets interface, so an existing client can point at it by changing the base URL and the key. Calls run through Monid and bill per request against your own wallet, so a quiet week costs almost nothing. It is an independent, Monid-backed implementation, not affiliated with or endorsed by Financial Datasets, and it ships no Financial Datasets data or code. When this doc calls a route “compatible,” it means the request and response shape match closely enough that an existing integration can switch base URLs and keep working, not that any code or data was copied.

​
Why per-call pricing

Most SEC research and market-data APIs charge a fixed monthly plan whether you make ten calls or ten thousand. That works for a trading desk. It doesn’t work for an agent that checks one company’s balance sheet twice a week. Each call here routes through SEC EDGAR, DefiLlama US equities, and Context.dev via Monid. Across the 51 priced calls in the committed receipts ledger, cost ran $0.0006 to $0.0100 with a mean of $0.00101 and a median of $0.0006; 82% of calls sat at the $0.0006 floor. You bring your own Monid API key, and every call bills your wallet directly. We take no cut and never see or store the key. The plan this replaces bills by request count: $200/month for Build with 100,000 requests included ($10 per additional 1,000), or $2,000/month for Scale with 1,000,000 included ($5 per additional 1,000). Both work out to $0.002 per included request, so the difference that matters here is the floor, not the unit rate: that $200 is due before the first request, while the whole ledger above cost $0.0515. Be aware of the other edge of per-call pricing. Our rate varies by route rather than being flat, and the most expensive routes here cost $0.0100 — five times the included rate. A high-volume workload made mostly of those routes is cheaper on a subscription, and we would rather say so than let you find out on an invoice. The scope isn’t complete. Some Financial Datasets routes aren’t implemented yet, and they answer with a typed, zero-cost not_implemented error rather than a guess. A few implemented routes cover less ground than the original, with capped result sizes and omitted fields in places. Read Compatibility before you build on this.

REST quickstart

Authenticate with X-API-KEY and pull an income statement.

MCP setup

Connect Claude, Cursor, or Claude Code to the MCP server at /mcp.

API Reference

Every REST endpoint, generated from the OpenAPI spec, with a request playground.

MCP Tools

All 27 tool names and parameters, generated from the tool schema file.

​
How the server is built

A success response contains only Financial Datasets schema keys, in schema property order. A field the server can’t source is left out of the response. It is never set to null or guessed.
If a route can’t be answered honestly, it returns {"error": "not_implemented", ...} at zero cost. Nothing is filled in with a plausible-looking number.
Each call the server makes to Monid, its run ID and its measured cost, is written to a receipts ledger. Cost is recorded per call, not estimated afterward.
get_filing_items extracts SEC filing sections with rule-based parsing against known section boundaries. There is no LLM in that path guessing where a section starts and ends.
Bring your own Monid API key. Every request, REST or MCP, sends it as the X-API-KEY header, and it bills your own Monid wallet. Get a key at monid.ai. See Authentication for how the header works.

​
Where to go next

Start with the Quickstart if you’re new. Go straight to MCP setup if you’re wiring an agent. Read Compatibility first if you’re deciding whether to migrate an existing Financial Datasets integration.