Agency concentration on company profiles
/api/v1/companies/{uei} now returns fpds_top_agency_share_pct: the share of a company's prime-contract obligations (FY2025 onward, from FPDS) flowing to its single largest awarding department. The comprehensive read of single-customer dependence, where the existing top_agency_share_pct sees only the sparse subset of contracts that carry a SAM Award Notice. For example GET /api/v1/companies/HNN4F9JZWDY8 (Palantir USG Inc) reads 94.5, nearly all of its FY2025+ obligations running through one department. Pro plan; silently omitted on non-Pro keys.
Agency abbreviations in contact lookup
/api/v1/contacts/lookup now resolves common agency abbreviations and codes in the agency filter to the agency name as stored, so agency=DLA returns Defense Logistics Agency contacts, agency=VA Veterans Affairs, and agency=GSA General Services Administration. Previously the value had to match the stored full agency name exactly, so the abbreviation everyone actually types returned nothing. Pro plan.
Every data source on one page, and how current it is
Every dataset we serve now has one page, /data, that lays out what each source is, its coverage window, the upstream system and its publishing cadence, and the exact current-as-of date, read live from GET /api/v1/status rather than hand-maintained. Where the most recent weeks of a source look thin, it notes that the upstream system has not reported those records yet, not that we are behind. The same numbers are available programmatically on /api/v1/status. See the data sources →
Recompete Watchlist API
See the contracts in your market that must recompete before they hit SAM. /api/v1/recompetes takes a market (NAICS, agency, set-aside, geography, value) and a window you choose, and returns the contracts entering their recompete window with the bid/no-bid facts: the incumbent, the value, the option runway, whether it was genuinely competed, and named subcontractors. Plus a live feed of sources-sought and pre-solicitation notices with the contracting officer's contact, to get on the radar before the RFP. Factual, not scored. Pro plan. Recompete Watchlist guide →
Teaming Partner Finder API
Find federal contractors with proven past performance, not just who is registered. /api/v1/partners/search takes a NAICS, awarding agency, place-of-performance state, or set-aside and returns the firms that have actually won matching prime contracts, ranked by obligated dollars, each with its socioeconomic status, SAM registration, and named points of contact. The only contractor endpoint that filters by awarding agency and returns who to call. Factual, not scored. Pro plan. Teaming Partner Finder guide →
Report a wrong response from the response
Every response under /api/v1/* carries a top-level _report_url. Open it in a browser and you land on a single-textarea form pre-filled with the exact call you just made. Type what you expected versus what you got, hit Send, and it emails the team directly, no portal login. The signed link is valid for 24 hours and bound to the customer who generated it, so don't paste a response containing this field into a public Slack or issue tracker.
Federal prime contracts (FPDS) API
Every federal prime contract transaction as clean JSON: base award and every modification, from the federal procurement system of record (FPDS), contract types A, B, C, and D. Three endpoints: /api/v1/contracts/search (by recipient UEI, PIID, agency, NAICS, award type, action date, obligation), /api/v1/contracts/{piid} (latest action plus a roll-up across every action under the PIID), and /api/v1/contracts/{piid}/modifications (the full modification trail). Coverage is FY2025 + FY2026: 9 million+ transactions, 8 million+ distinct contracts, 100,000+ recipients, refreshed daily. Contracts API guide →
FPDS contract context on the rest of the API
On endpoints you're already calling, Pro responses now include FPDS prime contract context inline alongside the subaward enrichment shipped previously. Same pattern, parallel data layer. A few concrete examples from prod, same keys, same auth:
GET /api/v1/companies/CKV2L9GZKJK3 (Deloitte Consulting LLP) now returns fpds_obligated_total of $4.18B across fpds_transaction_count 2,808 transactions on fpds_distinct_contracts 908 prime contracts, plus fpds_top_naics and fpds_top_agencies. The full federal activity picture in one call, alongside the existing SAM Award Notice slice.GET /api/v1/entities/{uei} and GET /api/v1/entities/by-cage/{cage} gain the same fpds_obligated_total and date-bound activity fields on the entity response.GET /api/v1/vendor-risk/{uei} gains a contract_exposure block alongside the existing subaward_exposure: obligation flow, top awarding agencies, action-date bounds. Compliance teams read both sides of the supply-chain blast radius in one screen.GET /api/v1/exclusions/{uei_sam} gains a recent_contract_actions block: is this excluded UEI still receiving direct prime contract obligations? Combined with recent_sub_payments, the compliance question goes from "are they debarred?" to "is anyone in the federal supply chain still paying them, directly or indirectly?" in one call.
All blocks are silently omitted on non-Pro keys; existing integrations keep working unchanged. _sources composes the underlying sources whenever the enrichment fires. Contracts API guide →
Dense subaward enrichment on contract detail
/api/v1/contracts/{piid} returns a subaward_rollup block on Pro keys summarizing the FFATA subaward footprint flowing from this prime contract: sub count, total subcontracted, share of the prime obligation, distinct sub-vendors, first and last dates, and the top 5 named sub-vendors. The PIID join is dense: within FY2025+ roughly 88% of subaward filings match a prime row, and 98% of in-scope contracts with subaward activity get a populated block. _sources extends to ["usaspending_fpds", "usaspending_ffata"] when the block fires.
Source attribution on every response
Every response under /api/v1/* now carries a top-level _sources array naming where the data came from: sam_opportunities, sam_entities, sam_exclusions, usaspending_fpds, usaspending_ffata, derived_duns_uei_crosswalk, derived_vendor_risk. Endpoints that compose multiple sources list each one. Customers reading _sources know exactly what to verify upstream when something looks off, without reading the per-endpoint documentation.
Money filter aliases across the obligation-flow cluster
/contracts/search, /awards/search, and /subawards/search accept both amount_min / amount_max and value_min / value_max as the same filter. /opportunities/search accepts both forms too. Cross-endpoint scripts no longer need to remember which name lives on which surface. Sending both forms at once returns a 400.
