shipapis
StarSubmit an APISubmit API

Data.gov vs EPA

Same instrument, two spec sheets — measured, not claimed.

APIData.govHEALTHY79EPAHEALTHY53
Uptime · 30d
Uptime · 90d100%54.9%
Uptime · 30d100%66.7%
P50 · ms9313150
P95 · ms20354966
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Data.gov vs EPA: common questions

Which is more reliable, Data.gov or EPA?

On our scheduled checks, Data.gov leads on measured uptime — Data.gov at 100% versus EPA at 54.9% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Data.gov or EPA?

Data.gov has the lower median latency in our checks — Data.gov responds in 931 ms versus EPA at 3150 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Data.gov and EPA need an API key?

Neither needs a paid key — Data.gov is callable with no signup, and EPA is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Data.gov and EPA from the browser?

Only EPA is browser-friendly — it returns CORS headers over HTTPS. Data.gov needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Data.gov and EPA free for commercial use?

Data.gov has unclear commercial terms, and EPA has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.