shipapis
StarSubmit an APISubmit API

OpenRegistry vs City, Toronto Open Data

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

APIOpenRegistryNEW—City, Toronto Open DataNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — no key required (CKAN)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenRegistry vs City, Toronto Open Data: common questions

Which is more reliable, OpenRegistry or City, Toronto Open Data?

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

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

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

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

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

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