Recipient Lookup API: Federal award recipient name resolution: fuzzy name in, deduplicated — USAspending and NIH RePORTER

Federal award recipient name resolution: fuzzy name in, deduplicated canonical recipient names (and UEI when available) out. The entity-resolution step before any who-got-federal-money question. Free, no key.

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

How do you call it?

GET /v1/funding/recipients — product id funding_recipient_lookup. Over MCP, call answerpool_get with product_id=funding_recipient_lookup.

curl "https://answerpool.io/v1/funding/recipients?q=lockheed"

Live call: https://answerpool.io/v1/funding/recipients?q=lockheed · JSON sample: /v1/samples/funding_recipient_lookup

What does the answer look like?

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

recipients

{
 "as_of": "2026-09-03T02:00:00Z",
 "count": 2,
 "recipients": [
  {
   "name": "LOCKHEED MARTIN CORPORATION",
   "uei": null
  },
  {
   "name": "LOCKHEED MARTIN CORP",
   "uei": null
  }
 ],
 "note": "Name resolution for award queries; UEI present when USAspending exposes it.",
 "disclaimer": "Reference data from USAspending.gov (US federal public domain); not procurement advice.",
 "refresh_after": "2026-09-18T00:00:00.000Z"
}

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

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

• USAspending (US federal public domain) — upstream: https://api.usaspending.gov/api/v2

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

When should you use it?

You are about to query federal awards by recipient and need the exact name variants the data uses.

What you skip building

• recipient name variant misses
• manual USAspending searching

When should you not use it?

SEC filer resolution — that is /v1/sec/cik.

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