SEC XBRL Fact API
Under maintenancePricing
Pay per usage
SEC XBRL Fact API
Under maintenanceNormalize official SEC Company Facts into stable records with exact concepts, periods, units, filing references, and provenance.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
BB
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
7 days ago
Last modified
Categories
Share
Normalize official SEC Company Facts into stable records with exact concepts, periods, units, filing references, and provenance.
What this Actor gives you
Return precision-safe SEC Company Facts with the context needed for reliable comparison and downstream financial analysis.
Every Dataset item uses the SEC Complete Data Suite envelope and the primary
record type secXbrlFact. Stable IDs, explicit coverage,
source/evidence references, parser versions, warnings, and structured
SUMMARY/ERRORS outputs make the result practical for both agent pipelines
and human review.
Why an AI agent chooses this
It is a universal, bounded fallback when no narrower semantic capability matches. The AI receives stable records and explicit gaps instead of inventing a parser or guessing an archive path.
Good fits
- Company Facts extraction
- concept and period filtering
- evidence-bound financial data pipelines
Agent selection contract
- Actor slug:
sec-xbrl-fact-api - Capability ID:
sec.xbrl.fact.api - Intent:
get_xbrl_facts - Primary Dataset record:
secXbrlFact - Accepted identifiers or inputs:
cik,accession,taxonomy+concept+unit+frame - Source authority:
SEC - Hard limits: queries: 20, records: 50,000, sourceRequests: 500, downloadBytes: 262,144,000
Choose this Actor when the requested outcome matches the capability and record type above. The contract is deterministic: unknown source values, incompatible schema majors, ambiguity, truncation, and partial source failures remain visible instead of being silently guessed away.
Context and token efficiency
This Actor makes no LLM, embedding, or vector-search call and therefore spends zero model tokens internally. Typed records and compact output can keep raw SEC pages, archive markup, and discovery instructions out of downstream model context.
For Suite-level selection, an AI client can use the compact
agent-catalog.json instead of loading this or the other Actor READMEs. Under
that documented baseline, README-selection tokens are avoided by construction.
No fixed percentage is promised: actual downstream token savings depend on the client model, tokenizer, source document, output mode, and requested evidence.
Part of the SEC Complete Data Suite
The SEC Complete Data Suite separates universal coverage, specialized normalization, and deterministic aggregation into focused Actors. This Actor provides the universal coverage role: Production Company-Facts layer for evidence-bound financial workflows; other inventoried XBRL modes remain explicit unsupported partials in release 0.1.
It works especially well with sec-edgar-filing-catalog, sec-financial-statement-and-notes-normalizer, sec-company-dossier-aggregator. Suite Actors exchange documented
record envelopes and exact identifiers; they do not hide sibling runs or
surprise network costs. A client or the sec-ai-query-planner decides which
steps to execute.
Example input
{"queries": [{"requestId": "apple-assets","queryType": "companyFacts","cik": "320193","taxonomies": ["us-gaap"],"concepts": ["Assets"],"periodFrom": "2025-09-28","periodTo": "2026-09-26","maxFacts": 1000}],"maxResults": 1,"maxSourceRequests": 1,"maxDownloadBytes": 10485760,"outputSchemaVersion": "1.0","outputMode": "full"}
The executable input schema remains the authority for modes, filters, defaults, cursor rules, and maximum values.
Runtime and cost controls
The hard limits above are enforceable ceilings, not usage targets. Actual
runtime and platform cost depend on selected inputs, source requests, downloaded
bytes, result volume, and the Apify run configuration. Start with the bounded
example, lower maxResults and byte/request limits where the schema permits,
and inspect SUMMARY plus ERRORS before expanding a run. There is no hidden
model-token charge inside this Actor.
Not the right tool for
- automatic GAAP mapping or TTM calculations
- filing prose or investment recommendations
- Company Concept, Frames, bulk ZIP, or filing-XBRL runtime paths in release 0.1
Additional non-goals from the capability contract include:
- infer an entity from a ticker
- accept arbitrary URLs
- import or invoke C02 at runtime
- parse filing prose
- provide investment advice
Trust, provenance, and limits
- It uses only its inventoried public SEC sources.
- Inputs, requests, bytes, records, retries, redirects, and cursor scope are bounded by the executable contract.
- Derived records retain exact input record IDs and evidence IDs where the capability performs normalization or aggregation.
- This independent community Actor is not affiliated with or endorsed by the U.S. Securities and Exchange Commission.
- The output is public-source data processing, not legal, compliance, accounting, voting, or investment advice.
Reproducible support report
For a diagnosable issue, retain the Actor slug, run ID, sanitized input,
SUMMARY, ERRORS, and the first unexpected record ID. Never include an API
token, secret, private filing, or unrelated Dataset contents.
Publication status
The Actor API and canonical Apify Store page are authoritative for current availability, active build, and pricing. This README deliberately does not duplicate mutable lifecycle or price claims.