BuyWhere vs Registrum API

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms440246
P95 · ms19011553
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BuyWhere vs Registrum API: common questions

Which is more reliable, BuyWhere or Registrum API?

On our scheduled checks, Registrum API leads on measured uptime — BuyWhere at 99.02% versus Registrum API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, BuyWhere or Registrum API?

Registrum API has the lower median latency in our checks — BuyWhere responds in 440 ms versus Registrum API at 246 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 BuyWhere and Registrum API need an API key?

Both ask you to authenticate — BuyWhere uses an API key and Registrum API 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 BuyWhere and Registrum API from the browser?

Neither sends browser-friendly CORS headers reliably, so call BuyWhere and Registrum API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are BuyWhere and Registrum API free for commercial use?

BuyWhere has unclear commercial terms, and Registrum 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.