Data API
Financial data API
FinUties exposes official, market, and thematic datasets behind one catalogue. Query by domain, keep provenance visible, and reuse the same resource names in apps and agents. We cover seven data domains and say how recent each should be; broader catalogue entries are research backlog unless marked otherwise.
Coverage clusters
- Filings & ownership — EDGAR-oriented paths and holdings
- Equities & markets — prices and related market series
- Rates & economics — policy and macro observations
- Positioning & calendar — CFTC-oriented and event schedules
Live path inventory: GET /api/v1/resources
(domains include a coverage flag: p0 vs research).
Example request
Discover first, then query — resource names are catalogue-driven.
# 1) Catalogue
curl -sS "https://data.finuties.com/api/v1/resources"
# 2) Query options for one resource
curl -sS -H "Authorization: Bearer $FINUTIES_TOKEN" \
"https://data.finuties.com/api/v1/resources/economics/<resource>/query-options"
# 3) Read
curl -sS -H "Authorization: Bearer $FINUTIES_TOKEN" \
"https://data.finuties.com/api/v1/economics/<resource>?limit=10"Illustrative JSON envelope:
{
"data": [{ "country": "DE", "period": "2026-Q1", "value": 0.3 }],
"meta": { "domain": "economics", "resource": "…", "count": 10 }
}Vs stitching scrapers
- One contract — same domain/resource names in REST, MCP, and Terminal.
- Honest freshness — P0 budgets (hours) for operator dashboards; inspect before production jobs.
- Metered clarity — token costs on responses instead of opaque per-row vendor deals.
- Claim discipline — marketing promises P0 density, not catalogue width.
One contract, three surfaces
- REST —
/api/v1/{domain}/{resource} - MCP —
POST /mcp/jsonrpcwith toolquery(MCP brief) - Terminal — open-source UI on the same catalogue