Bitbucket vs GeoNet API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3732533
P95 · ms15522808
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bitbucket vs GeoNet API: common questions

Which is more reliable, Bitbucket or GeoNet API?

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

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

GeoNet API needs no key, while Bitbucket requires a free API key. If you want to start calling without signup, reach for GeoNet API first.

Can I call Bitbucket and GeoNet API from the browser?

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

Are Bitbucket and GeoNet API free for commercial use?

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