Bitbucket Cloud API vs Currents

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms783586
P95 · ms16061165
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limit60, 60;w=3600 req/window · 59 remaining · resets 2635Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bitbucket Cloud API vs Currents: common questions

Which is more reliable, Bitbucket Cloud API or Currents?

Both are neck-and-neck — Bitbucket Cloud API and Currents 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, Bitbucket Cloud API or Currents?

Currents has the lower median latency in our checks — Bitbucket Cloud API responds in 783 ms versus Currents at 586 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 Bitbucket Cloud API and Currents need an API key?

Both ask you to authenticate — Bitbucket Cloud API uses an API key and Currents uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Bitbucket Cloud API and Currents from the browser?

Only Bitbucket Cloud API is browser-friendly — it returns CORS headers over HTTPS. Currents needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Bitbucket Cloud API and Currents free for commercial use?

Bitbucket Cloud API has unclear commercial terms, and Currents 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.