SEC EDGAR

Give your agent or app the filing behind every number.

Your agent asks about a public company. The value comes back with the filing that reported it.

The sandbox key works on Amprius Technologies (AMPX). No card is required.

Documents in many formats drop into the SourceKeel hull, run through its channel and leave through the keel as one API response, which then traces back to the filing it came from. collect keep the original serve PDF CSV XBRL XML HTML JSON the filing it came from GET /v1/companies/AMPX/facts"value": 28536000,"form": "10-Q","accession": "0001899287-26-000045"

Many sources in, one format out, and every value keeps its way back.

Livestatus
11datasets
57endpoints
1official source

What one request returns

You ask your agentWhat was Amprius Technologies' revenue for the first quarter of 2026?
Your agent answers$28,536,000 for the quarter that ended March 31, 2026.
Source: Form 10-Q, filed May 7, 2026, accession 0001899287-26-000045. Open the filing on sec.gov

The request behind that answer. The response is trimmed to the fields used here.

$ curl "https://api.sourcekeel.com/v1/companies/AMPX/facts?tags=Revenues" \
    -H "Authorization: Bearer $SOURCEKEEL_API_KEY"

{
  "canonical_tag": "Revenues",
  "raw_tag": "us-gaap:Revenues",
  "value": 28536000,
  "unit": "USD",
  "period_start": "2026-01-01",
  "period_end": "2026-03-31",
  "source": "SEC EDGAR",
  "form": "10-Q",
  "filing_date": "2026-05-07",
  "accession": "0001899287-26-000045"
}

The canonical_tag is the name SourceKeel uses for the line. The raw_tag is what the filing called it. The accession number identifies the filing, and a sandbox key can make this call as soon as you sign up.

When a number looks wrong

1

The response carries the value and the accession number of the filing that reported it.

GET /v1/companies/AMPX/facts?tags=Revenues
2

One request returns that filing's documents. Open the 10-Q and compare.

GET /v1/filings/0001899287-26-000045/documents
3

If the filing shows something else, report it with the value you got and the one you expected.

POST /v1/corrections
4

Follow the report until it has an answer.

GET /v1/corrections/{id}
POST /v1/corrections
{
  "subject": "AMPX",
  "field": "Revenues",
  "period_end": "2026-03-31",
  "returned_value": "28536000",
  "expected_value": "(the figure the filing shows)",
  "source_link": "https://www.sec.gov/Archives/edgar/data/1899287/000189928726000045/ampx-20260331.htm"
}

"status": "received"      then "reviewing"  (We are checking it against the filing)
                          then "confirmed", "fixed" or "not_an_error"

The same question, two ways

Without SourceKeel

  1. Find the 10-Q on EDGAR and download it.
  2. Find the tag that holds revenue in the filing.
  3. Reconcile it against the other filings for the same period.
  4. When a value is wrong, trace which record it came from and which filing that record came from.

With SourceKeel

  1. One request: GET /v1/companies/AMPX/facts?tags=Revenues
  2. The value and its filing arrive together.

When a company changes a number

Applied Digital reported current assets at May 31, 2025 as $430,593,000. A later 10-Q reports $132,800,000 for the same date. The API returns both values with both filings.

$ curl "https://api.sourcekeel.com/v1/companies/APLD/amendment-diffs" \
    -H "Authorization: Bearer $SOURCEKEEL_API_KEY"

{
  "relationship_type": "subsequent_filing_revision",
  "form": "10-Q",
  "accession": "0001144879-26-000030",
  "prior_accessions": ["0001144879-26-000006"],
  "affected_periods": [{ "period_end": "2025-05-31" }],
  "reported_value_changes": [{
    "metric_key": "current_assets",
    "original": { "accession": "0001144879-26-000006", "value": 430593000 },
    "current":  { "accession": "0001144879-26-000030", "value": 132800000 }
  }]
}

Trimmed. Applied Digital (APLD) is not in the sandbox, which serves AMPX.

I built SourceKeel so that a wrong number is quick to find and quick to fix. Read my letter on why it exists.Ola, Founder

HTTP, CLI and MCP

Call the HTTP API, use the command line tool, or connect an agent through the MCP server. They all read the same data with the same key.

export SOURCEKEEL_API_KEY=sk_sandbox_xxx   # sk_live_xxx on a paid plan
sourcekeelctl mcp stdio

Try it on Amprius Technologies

The free sandbox key works on every endpoint for Amprius Technologies. It needs no card.

Get a free sandbox key See pricing

Sign-in, account and form security, and your saved cookie choice.

Google Fonts and the interactive reference from unpkg. These providers receive browser request information.

Read the cookie inventory.