CIE-10 API vs City Bikes

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms271404
P95 · ms24461429
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limit120 req/window · 119 remaining · resets 1783518425300 req/window · 296 remaining · resets 837
In directory since2026-07-052026-07-05
operationalpartialdownno data

CIE-10 API vs City Bikes: common questions

Which is more reliable, CIE-10 API or City Bikes?

Both are neck-and-neck — CIE-10 API and City Bikes each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, CIE-10 API or City Bikes?

CIE-10 API has the lower median latency in our checks — CIE-10 API responds in 271 ms versus City Bikes at 404 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do CIE-10 API and City Bikes need an API key?

Neither needs a paid key — CIE-10 API is callable with no signup, and City Bikes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call CIE-10 API and City Bikes from the browser?

Yes — both CIE-10 API and City Bikes 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 CIE-10 API and City Bikes free for commercial use?

CIE-10 API has unclear commercial terms, and City Bikes 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.