City, New York Open Data vs Data.gov

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
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

City, New York Open Data vs Data.gov: common questions

Which is more reliable, City, New York Open Data or Data.gov?

On our scheduled checks, Data.gov leads on measured uptime — City, New York Open Data at —% versus Data.gov 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 City, New York Open Data and Data.gov need an API key?

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

Can I call City, New York Open Data and Data.gov from the browser?

Only City, New York Open Data 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 City, New York Open Data and Data.gov free for commercial use?

City, New York Open Data has unclear commercial terms, and Data.gov 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.