City, New York Open Data vs OpenRegistry

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

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

City, New York Open Data vs OpenRegistry: common questions

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

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

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

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

Yes — both City, New York Open Data and OpenRegistry send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are City, New York Open Data and OpenRegistry free for commercial use?

City, New York Open Data 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.