shipapis
StarSubmit an APISubmit API

Data.gov vs OpenRegistry

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

APIData.govNEW—OpenRegistryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Data.gov vs OpenRegistry: common questions

Which is more reliable, Data.gov or OpenRegistry?

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

Do Data.gov and OpenRegistry need an API key?

Data.gov needs no key, while OpenRegistry requires a free API key. If you want to start calling without signup, reach for Data.gov first.

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

Only OpenRegistry 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 OpenRegistry free for commercial use?

Data.gov has unclear commercial terms, and OpenRegistry 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.