BdAPIs vs Postcodes.io

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms81733
P95 · ms1250328
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedService MIT-licensed; postcode data license unverified
Free tierFree, no API keyFree — no key required
Rate limit100 req/window · 98 remaining · resets 324Unpublished (no key; fair use)
In directory since2026-07-052026-07-05
operationalpartialdownno data

BdAPIs vs Postcodes.io: common questions

Which is more reliable, BdAPIs or Postcodes.io?

Both are neck-and-neck — BdAPIs and Postcodes.io 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, BdAPIs or Postcodes.io?

Postcodes.io has the lower median latency in our checks — BdAPIs responds in 817 ms versus Postcodes.io at 33 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 BdAPIs and Postcodes.io need an API key?

Neither needs a paid key — BdAPIs is callable with no signup, and Postcodes.io is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call BdAPIs and Postcodes.io from the browser?

Yes — both BdAPIs and Postcodes.io 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 BdAPIs and Postcodes.io free for commercial use?

BdAPIs has unclear commercial terms, and Postcodes.io 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.