City, New York Open Data vs District of Columbia Open Data

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (DC Open Data terms)
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 District of Columbia Open Data: common questions

Which is more reliable, City, New York Open Data or District of Columbia Open Data?

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

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

Can I call City, New York Open Data and District of Columbia Open Data from the browser?

Yes — both City, New York Open Data and District of Columbia Open Data 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 District of Columbia Open Data free for commercial use?

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