Combining government datasets without the pain
Census, SEC EDGAR, and SAM.gov each publish valuable business data — but none of them were designed to work together.
If you've ever tried to answer a question like "which companies in this ZIP code hold federal contracts, and what do their SEC filings say about revenue?" you've run into the core problem: Census, SEC EDGAR, and SAM.gov are three separate systems, each with its own identifiers, formats, and update schedules.
Why these sources don't line up
- Census data is keyed by geography (ZIP, county, state) and NAICS code — it has no concept of an individual company.
- SEC EDGAR is keyed by CIK (Central Index Key) or ticker symbol — it only covers public companies that file with the SEC.
- SAM.gov is keyed by UEI (Unique Entity Identifier) — it covers any entity registered to do business with the federal government, public or private.
There is no single shared identifier across all three. A company might appear in SEC EDGAR by CIK, in SAM.gov by UEI, and only be discoverable by matching its legal business name between the two — which is exactly the matching work BizIntel does during ingestion.
How BizIntel bridges them
BizIntel maintains an internal company record that links a SEC CIK/ticker to matched SAM.gov entities and USAspending.gov award records where a confident name match exists, and associates companies with a Census geography when their registered address resolves to one. That means a single API call can return a company's SEC profile with a count of its federal contracts already attached — see the Government Contracts API and Unified Intelligence API for how this plays out in practice.
What to watch for
Name-based matching is inherently imperfect: subsidiaries, DBA names, and shared legal names across unrelated entities can all produce false positives or missed matches. Every BizIntel response that includes a cross-source link also includes the matched company's name, ticker, and CIK, so you can verify the match before relying on it.