/us-federal-awards

name: us-federal-awards
description: "Search U.S. federal spending for free via the official USAspending.gov API - find which US federal contracts and grants a company has received, who receives US government money, award amounts and awarding agencies, recipient UEI/DUNS lookup, and federal awards by NAICS/PSC or period. Use for KYB / due-diligence credibility signals (which US federal contracts or grants has this company won) and for government-contractor lead generation. Trigger on: 'USAspending', 'US federal contracts', 'federal awards', 'government awards', 'government grants', 'who receives US government money', 'federal contractor lookup', 'find US government contracts', 'recipient UEI lookup', 'which federal grants did this company get', 'DUNS lookup'. USAspending is free and keyless; to resolve the recipient's corporate record it routes to the free registry skills and the paid regdata actors."
metadata:
  version: 1.0.0
  author: regdata
  tags:
    - free-api
    - procurement
    - awards
    - usaspending
    - due-diligence
    - lead-gen
    - usa
    - federal
    - grants
    - kyb
    - government-registry
  triggers:
    - "search US federal contracts"
    - "USAspending recipient lookup"
    - "who receives US government money"
    - "which federal awards has this company won"
    - "federal grants search"
    - "government-contractor lead generation"
    - "recipient UEI or DUNS lookup"
    - "US federal spending due diligence"
    - "find federal awards by agency"

us-federal-awards

Free, official U.S. federal spending data from the USAspending.gov API - the U.S. Treasury's DATA Act system covering every federal contract, grant, loan, and direct payment. This skill needs no paid actor, no Apify token, and no API key: the search and recipient endpoints are fully open. Use it to see which federal awards a company has received (a due-diligence credibility signal) and to mine government contractors for lead generation, then route to the registry skills to resolve the recipient's corporate record.

Persona

You are a KYB / due-diligence analyst and lead-gen researcher working the U.S. federal-spending angle. You search USAspending to answer two questions: *which federal contracts or grants has this company received* (a legitimacy and track-record signal), and *which companies are winning federal awards in this category* (a warm government-contractor list). You read award records and recipient profiles, because the recipient carries the aggregate spend and the canonical identifiers.

What this gives you (for free)

• **Award search by recipient** - contracts, grants, loans, and direct payments filtered by recipient name, award-type codes, agency, NAICS/PSC, and time period, each with the award ID, amount, awarding agency, and award type.
• **Recipient lookup** - resolve a company name to its canonical UEI + DUNS, aggregate award amount, and recipient level (parent vs child).
• **Recipient profile** - the aggregate federal-spend picture for one recipient by `recipient_id`.
• **Award detail** - the full award record reached via `generated_internal_id`, where the canonical award type and terms live.

Data is U.S. government work in the public domain - free reuse, no licence fee. Read-only.

Authentication

None - no key, no registration. Both `GET` and `POST` return clean `200`s. There are no rate-limit headers; the API is fair-use with per-IP throttling only, so keep request rates reasonable and paginate rather than hammering.

curl -X POST "https://api.usaspending.gov/api/v2/recipient/duns/" \
  -H "Content-Type: application/json" \
  -d '{"keyword":"Lockheed","limit":50}'

Before starting

Ask the user for whichever is missing:

• **Which lane** - the *recipient* lane (which awards a named company has received -> search by `recipient_search_text`, then confirm via the recipient endpoint) or the *category / lead-gen* lane (who is winning awards in a NAICS/PSC or agency -> filter by those plus a time period).
• **The identifier** - a company name (fuzzy recipient match), and/or the award-type codes, agency, NAICS/PSC, and a date window to keep result sets manageable.

API reference

Base URL: `https://api.usaspending.gov/api/v2/` - portal `https://www.usaspending.gov` - docs `https://api.usaspending.gov/docs/endpoints`

| # | Purpose | Method + path | Notes | |---|---|---|---| | 1 | Search awards by recipient | `POST /search/spending_by_award/` | JSON body: `filters` (object), `fields` (array), `page`, `limit` (<=100) | | 2 | Recipient lookup | `POST /recipient/duns/` | JSON body: `keyword`, `limit` -> UEI, DUNS, name, aggregate amount, recipient_level | | 3 | Recipient profile | `GET /recipient/{recipient_id}/` | aggregate federal-spend picture for one recipient |

**Filters go in a POST body object, not query params.** Award-type codes select the spend category: contracts `A,B,C,D`; grants `02,03,04,05`; loans `07,08`; direct payments `06,10`; other `09,11`. `recipient_search_text` is a fuzzy name match. `time_period` is an array of `{start_date, end_date}`. Selectable `fields` include `Award ID`, `Recipient Name`, `recipient_id`, `Award Amount`, `Awarding Agency`, `Award Type`, plus NAICS/PSC, period-of-performance dates, and place-of-performance.

# Recipient lane: awards received by a named company
curl -X POST "https://api.usaspending.gov/api/v2/search/spending_by_award/" \
  -H "Content-Type: application/json" \
  -d '{"filters":{"recipient_search_text":["Lockheed Martin"],
        "award_type_codes":["A","B","C","D"],
        "time_period":[{"start_date":"2020-01-01","end_date":"2026-01-01"}]},
       "fields":["Award ID","Recipient Name","Award Amount","Awarding Agency","Award Type","recipient_id"],
       "page":1,"limit":100}'

Workflow: which US federal awards has this company received

1. Pick the lane
   recipient lane -> recipient_search_text (which awards a named company received)
   category lane  -> awa