Everything EDGAR says about earnings, structured and cited. One key.

Report dates marked confirmed or estimated, results and fundamentals with the filing behind every number, insider trades and the filing index, for every US-listed company worth $300M or more. Decide on filings, not feeds.

Built only from SEC EDGAR and company announcements. Free account with GitHub or Google: 100 calls, no card.

GET/v1/next/ACME
{
  "ticker": "ACME",
  "fiscal_period": "Q3 FY2026",
  "report_date": "2026-11-04",
  "timing": "AMC",
  "call_time_et": "16:30",
  "status": "confirmed",
  "source_url": "https://ir.acme.example/news/q3-2026-date",
  "confirmed_at": "2026-10-16T13:02:11Z",
  "webcast_url": "https://ir.acme.example/events",
  "status_help": "The company has announced this date (see source_url)."
}
Every date carries a status and a source_url. An estimate says so in the response, so nothing downstream can mistake it for a confirmation.

Why not just ask your AI?

Ask an assistant when a company reports and it will search the web and pick a page. It can't tell a company's announcement from a calendar site's estimate, and it won't tell you which one it found. You get a confident sentence and no way to check it.

Veritas gives the model, and you, the same thing every time: the date, whether the company confirmed it, and the document that proves it. When the answer is an estimate, the response says so.

  • Every date carries a status and a source URL. Nothing is shown as confirmed unless the company said it.
  • Built only from SEC filings and company announcements. No vendor data of unknown origin anywhere in the chain.
  • Works inside the tools people already use. The MCP server's tool descriptions tell the model what estimated means, so the caveat survives the trip from our database to the chat window.

How a date gets its status

A date moves through three states, and the API tells you which one it is in. Nothing is ever invented: with no usable history the answer is unknown, not a guess.

1

Estimated from filing cadence

We read the company's 10-Qs, 10-Ks and past earnings 8-Ks from EDGAR and project the next date from how it has reported before, with a confidence score.

estimated
2

Confirmed by the company

When the company announces the date in a press release or filing, the event becomes confirmed and links to that document. If the date later moves, you see the change.

confirmed
3

Reported

When the results 8-K hits EDGAR, the event closes with the actual date and time, and the next quarter's estimate opens.

reported

Coverage and accuracy

62.3% of our estimated dates landed within 3 days of the actual report, measured on 18,346 releases since 2024, estimated 5 days after each quarter closed.

62.3%estimates within 3 days
52.9%within 1 day
36.9%exact date
18,346releases scored
3,216companies tracked
2004earnings releases on record since
164,6648-K earnings releases stored
122company announcements captured

Measured 2026-11-08: every release since 2024-11-08 replayed from 5 days after its quarter ended, using only the filings visible then. Percentages are of all releases, so a release we gave no estimate for counts as a miss. Company-confirmed dates are not included; they come from the company. Live figures: /v1/coverage.

Compared with the incumbent

Facts only, as published by each provider; checked November 2026. Tell us if something has changed.

Veritas Datasec-api.io
Free tierFree account: 100 calls, every endpoint and every company, REST and MCP100 calls, lifetime, API only
Paid entry$19 a month, every company, 10,000 requests a day$49 to $55 a month personal; $199 to $239 business
Source on every numberYes: source_url, accession and tag on each valueFiling URLs on filing records
Earnings dates with confirmed / estimated statusYes, with the announcement or the cadence basisNot offered
MCP serverIncluded, X-API-Key or OAuthNot listed
Redistribution licenceBuilder planPer contract

Sources: sec-api.io pricing (checked 2026-11); Veritas pricing and docs.