Company Crosswalk API: A company resolved across SEC EDGAR and federal spending in one call — free lookup

A company resolved across SEC EDGAR and federal spending in one call: exact CIK plus candidate USAspending recipient names, each graded exact/strong/weak because the join is by name, not by key. Free, no key.

Free — no key, no signup, rate-limited to 60 calls per minute per client.

How do you call it?

GET /v1/sec/crosswalk — product id sec_crosswalk. Over MCP, call answerpool_get with product_id=sec_crosswalk.

curl "https://answerpool.io/v1/sec/crosswalk?ticker=LMT"

Live call: https://answerpool.io/v1/sec/crosswalk?ticker=LMT · JSON sample: /v1/samples/sec_crosswalk

What does the answer look like?

A representative response, the same static sample served at /v1/samples/sec_crosswalk.

federal_recipients

{
 "as_of": "2026-09-03T15:30:00Z",
 "query": "LMT",
 "sec": {
  "source": "sec_edgar",
  "identifier_kind": "cik",
  "identifier": "0000936468",
  "label": "LOCKHEED MARTIN CORP",
  "next_url": "/v1/sec/entity?cik=0000936468",
  "confidence": "exact"
 },
 "federal_recipients": [
  {
   "source": "usaspending",
   "identifier_kind": "recipient_name",
   "identifier": "LOCKHEED MARTIN CORPORATION",
   "label": "LOCKHEED MARTIN CORPORATION",
   "next_url": "/v1/funding/recipients?q=LOCKHEED",
   "confidence": "exact"
  }
 ],
 "note": "The SEC leg is an exact identifier resolution; federal-spending legs are NAME matches (no public key links a CIK to a recipient). exact = same name once corporate suffixes are stripped; strong = the name extends it, usually a subsidiary or affiliate rather than the same legal entity; weak = a looser match that may be an unrelated company. Absence of a federal match is not evidence the company holds no federal awards.",
 "disclaimer": "Derived from public SEC EDGAR filings; not investment advice.",
 "refresh_after": "2026-09-17T11:15:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15:00.000Z. Schedule the next call on that value rather than on a guess.

• SEC EDGAR (US federal public domain) — upstream: https://efts.sec.gov

Method version 0.1.0 · serving cache 1 day · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

You have a company and need its identity in both the SEC and federal-spending worlds.

What you skip building

• hand-built CIK-to-recipient mappings
• corporate suffix mismatches
• assuming a name match is an entity match

When should you not use it?

Spending amounts and trajectories — /v1/funding/signals; SEC-only resolution — /v1/sec/resolve.

Where else can you find this?

• Catalog entry (JSON, free)
• OpenAPI schema — input and output types, prices, the 402 flow
• llms.txt — every product in one plain-text document