Spending Resolver API: Any federal-spending string — USAspending and NIH RePORTER
Any federal-spending string in — industry, product, program, recipient or agency — every code space searched at once, each match tagged with the filter parameter it belongs to. One call instead of five lookups. 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/resolve — product id
funding_resolve. Over MCP, call answerpool_get with
product_id=funding_resolve.
curl "https://answerpool.io/v1/funding/resolve?q=cancer"
Live call: https://answerpool.io/v1/funding/resolve?q=cancer · JSON sample: /v1/samples/funding_resolve
What does the answer look like?
A representative response, the same static sample served at /v1/samples/funding_resolve.
as_of | 2026-09-03T15:00:00Z |
|---|---|
query | cancer |
count | 2 |
note | Searches every federal code space at once — NAICS, PSC, assistance listing, recipient, agency — so one call replaces guessing which lookup applies. |
disclaimer | Reference data from USAspending.gov (US federal public domain); not procurement advice. |
refresh_after | 2026-09-18T00:00:00.000Z |
matches
| kind | code | label | filter_param |
|---|---|---|---|
| program | 93.398 | Cancer Research Manpower | program_number |
| naics | 621512 | Diagnostic Imaging Centers | naics |
The same sample as raw JSON
{
"as_of": "2026-09-03T15:00:00Z",
"query": "cancer",
"count": 2,
"matches": [
{
"kind": "program",
"code": "93.398",
"label": "Cancer Research Manpower",
"filter_param": "program_number"
},
{
"kind": "naics",
"code": "621512",
"label": "Diagnostic Imaging Centers",
"filter_param": "naics"
}
],
"next_endpoints": [
{
"path": "/v1/funding/signals",
"url": "/v1/funding/signals?term=cancer",
"description": "Federal funding trajectory for this term (USAspending + NIH)",
"price_usd": 0.02
}
],
"note": "Searches every federal code space at once \u2014 NAICS, PSC, assistance listing, recipient, agency \u2014 so one call replaces guessing which lookup applies.",
"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.
What should you call next?
- funding_signals — Federal funding trajectory for this term (USAspending + NIH) ($0.02)
When should you use it?
You have one string and do not know which federal code space it belongs to.
What you skip building
- five sequential autocomplete calls
- picking the wrong code space
When should you not use it?
You already know the space — call that lookup directly for more results.
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