# Belfort Data API

> Company figures from U.S. SEC filings. Every figure names the filing it came from, and the error rates are published.

The Belfort Data API serves company figures that come only from filings with the U.S. Securities and Exchange Commission: key metrics, financial statements as filed, segment revenue, insider trades, Form 13F holdings, filings lists, earnings releases, and two official macro series. It's read-only, it answers in JSON, and an MCP server puts the same data in front of AI agents.

Two things set it apart. Every figure tells you which filing it came from, so you can open the filing and check it. And we publish how often our figures are wrong, with the sample sizes behind each number.

## Start here

- **[Quickstart](/quickstart/)**: from an API key to your first answer, in curl, Python or TypeScript.
- **[Datasets](/datasets/)**: what each route returns, where it comes from, and what to watch for.
- **[Where the data comes from](/data-sources/)**: the SEC and BLS sources behind each dataset, and how a figure keeps its filing.
- **[Quality](/quality/)**: measured error rates, sample sizes and methods, including what we haven't measured yet.
- **[API reference](/api-reference/)**: every route and field, with a console that sends real requests.
- **[MCP server](/mcp/)**: use the data from Claude Desktop, Claude Code or another MCP client.

## Base URL and your key

Base URL:

```text
https://belfort-data-api.vercel.app
```

Send your key in the `X-API-Key` header on every route except `/v1/status`. A company can be named by ticker, in any case, or by CIK with or without leading zeros. The full rules are in [Requests and responses](/requests-and-responses/).

:::note[Pilot]
The API is in a private pilot. Keys are issued by Belfort; see [Pricing](/pricing/). Data is derived from filings on the SEC's EDGAR system. Belfort is not affiliated with or endorsed by the SEC. This is data, not investment advice.
:::

---
Source: https://docs.belfortagent.xyz/