Government and public data is quietly one of the largest verticals in the catalog — 368 providers — and one of the most underrated. These aren’t startups chasing revenue; they’re agencies that have, often slowly, turned public records into programmable surfaces. The catalog treats a federal data API with the same lens as a commercial one, which is exactly the comparison that makes the gaps visible.
The bands
| Band | What it does | Providers on apis.io |
|---|---|---|
| Environmental & scientific | Air, water, climate, space | EPA (31 APIs), NASA (17), NOAA (12), USGS Water (10) |
| Health & regulatory | Drugs, devices, benefits | openFDA (17), CMS (10), NHS Digital (15) |
| Services & administration | Procurement, mail, veterans | GSA (31), USPS (12), VA (23) |
What’s shifted recently
- Decomposition by program, not by portal. The leading agencies — EPA, NASA, openFDA — now publish many narrow APIs instead of one mega-endpoint. The EPA’s ECHO family splits by statute; openFDA splits by drug, device, and food. That’s the same per-product decomposition the best commercial publishers use.
- Streaming and operational data. Agencies are moving past static downloads. The EPA’s power-sector emissions surface includes streaming services; weather and water APIs are real-time. Public data is becoming live infrastructure, not an annual report.
- A widening quality gap. The catalog’s scoring makes it plain: a handful of agencies publish OpenAPI, auth docs, and changelogs; many still ship an undocumented endpoint and a PDF. The structure is uneven, and now it’s measurable.
Where to start
- The Government industry page ranks all 368 providers.
- For the gold-standard decomposition, read the EPA profile — 31 program-aligned APIs.
- For procurement and federal services, GSA (31 APIs) is the anchor.
The takeaway
Public data is where the catalog does civic work: by holding agencies to the same structural standard as commercial APIs, it shows which ones have made their data genuinely usable and which still hide it behind a download link. The leaders prove that a regulatory dataset and a clean API contract are not in tension.