DealChartsby CMD+RVL

SEC EDGAR CompanyFacts API

Find SEC EDGAR CompanyFacts JSON paths like CIK0001018724, XBRL endpoints, fair-access rules, and DealCharts links from filings to structured-finance context.

Developer and analyst entrypoint

Find the SEC CompanyFacts JSON. Keep the structured-finance context.

The SEC gives you public filing JSON, including CompanyFacts paths by CIK. DealCharts helps connect that source data to deals, funds, source documents, and facts endpoints you can cite.

View endpoint map

Open API docs

Quick answer

CIK0001018724 CompanyFacts URL

Filing entityAmazon.com, Inc. (CIK0001018724)
SEC sourcedata.sec.gov/api/xbrl/companyfacts/CIK0001018724.json
DealCharts layerCIKs, filings, facts JSON, source documents, and structured-finance context
Page updatedJuly 5, 2026

What the SEC APIs Give You

The SEC's public developer documentation separates EDGAR data access from filer-submission APIs. For data analysis, the important public surfaces are submissions history and extracted XBRL facts served as JSON on

data.sec.gov
.

Official SEC data APIs

Public JSON, no data API key

The SEC describes

data.sec.gov
as RESTful JSON APIs for submissions by company and extracted XBRL data. The SEC API page says these data APIs do not require authentication or API keys.

SEC EDGAR API documentation

Fair access

Declared User-Agent and 10 requests per second

SEC guidance asks automated users to declare a User-Agent, download only what they need, and keep request rates within the current 10 requests per second fair-access limit.

Where DealCharts Adds Structure

Raw EDGAR is the source. DealCharts is the read layer for structured-finance context built from those public filings. Use it when the task is not just "fetch a filing," but "connect this filing, CIK, fund, deal, or chart to a citable structured-finance object."

Entity resolution

Move from CIKs to deal and fund pages

Search resolves issuer names, fund names, deal slugs, BDC tickers, and structured-finance entities into stable DealCharts pages and facts paths.

Machine-readable facts

Use facts JSON for agents and scripts

Facts files carry identifiers, dates, source documents, provenance, citation text, and page URLs for downstream research, retrieval, and audit trails.

Data model

Keep ontology and source documents visible

The ontology maps FilingDocument, Deal, Tranche, Fund, Counterparty, Chart, and Dataset objects so your application can distinguish source filings from DealCharts projections.

Human workflow

Route hard questions to CMD+RVL

If you need a custom monitor, bulk pull, or filing-state workflow, CMD+RVL can scope the data path without moving evidence logic into DealCharts.

Structured-Finance Workflows

  1. CIK to filing history

    Find the filing universe first

    Use SEC submissions JSON for a 10-digit CIK such as

    CIK0001018724
    . Then search DealCharts when you need structured-finance exposure, deal pages, or facts JSON tied to that filing entity.

  2. 10-D and ABS surveillance

    Connect remittance filings to deal objects

    Use EDGAR for source filings. Use DealCharts to inspect CMBS and Auto ABS deal pages, chart paths, facts JSON, and source document references for normalized surveillance context.

  3. Fund holdings

    Bridge NPORT-P disclosures into fund facts

    Fund pages expose NPORT-P-derived holdings context and facts JSON, useful when a model or analyst needs a source-backed answer to who holds a structured-finance position.

  4. AI retrieval

    Prefer citable facts over scraped snippets

    Retrieval agents can pair

    llms.txt
    , facts endpoints, and ontology references with SEC source URLs to ground answers in public filings and stable DealCharts IDs.

Endpoint Map

EndpointUse it forSource or layer
https://data.sec.gov/submissions/CIK##########.jsonCurrent filing history by 10-digit CIK, including recent filings and entity metadata.SEC
https://data.sec.gov/api/xbrl/companyfacts/CIK##########.jsonAll non-custom taxonomy XBRL concepts for a filing entity in one JSON call.SEC
https://data.sec.gov/api/xbrl/companyconcept/CIK##########/us-gaap/AccountsPayableCurrent.jsonOne XBRL concept for one company, grouped by unit of measure.SEC
https://dealcharts.org/.netlify/functions/search?query=blackrockResolve names, funds, BDCs, deals, and counterparties into DealCharts pages.DealCharts
https://dealcharts.org/llm/facts/{entity_key}.jsonMachine-readable structured-finance facts with identifiers, dates, source links, and provenance.DealCharts
https://dealcharts.org/ontology/Entity and relationship model for deals, filings, tranches, funds, counterparties, charts, and datasets.DealCharts

Examples to Copy

# SEC submissions history for Amazon.com, Inc. from the search query pattern
curl -H "User-Agent: Your Company name@example.com" \
https://data.sec.gov/submissions/CIK0001018724.json
# SEC CompanyFacts JSON for the same CIK
curl -H "User-Agent: Your Company name@example.com" \
https://data.sec.gov/api/xbrl/companyfacts/CIK0001018724.json
# Resolve a structured-finance name in DealCharts
curl "https://dealcharts.org/.netlify/functions/search?query=blackrock"
# Pull a DealCharts facts file
curl https://dealcharts.org/llm/facts/bmark2021-b28.json

Frequently Asked Questions

Is DealCharts a replacement for
data.sec.gov
?

No.

data.sec.gov
is the SEC source for submissions history and XBRL data. DealCharts is useful after that first fetch, when you need the structured-finance layer: deal pages, fund exposure, facts JSON, source links, ontology, and datasets.

Does SEC EDGAR API access require an API key?

The public SEC data APIs on

data.sec.gov
do not require authentication or API keys, according to the SEC API documentation. Automated access still has fair-access duties: declare a User-Agent, moderate requests, and download only what you need.

Where do I find SEC CompanyFacts JSON for
CIK0001018724
?

CIK0001018724
is Amazon.com, Inc. The SEC endpoint is
https://data.sec.gov/api/xbrl/companyfacts/CIK0001018724.json
. DealCharts helps when you need to connect a CIK or filing entity to structured-finance deals, funds, source documents, or facts JSON.

What should I use for agent retrieval?

Start with

,
/api/
,
/ontology/
, and entity facts files. Pair DealCharts facts with SEC source URLs whenever your answer needs citation.

Powered by CMD+RVL

DealCharts is the public projection surface for structured-finance data: crawlable deal, fund, BDC, and dataset references with source-aware context.

© 2026 CMD+RVL. All rights reserved.·Not investment advice. For informational purposes only.·Built 2026-07-09