shipapis
StarSubmit an APISubmit API

BuyWhere vs Lookup.im API

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

APIBuyWhereHEALTHY86Lookup.im APIHEALTHY84
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%100%
P50 · ms4401158
P95 · ms19013581
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 Lookup.im API: common questions

Which is more reliable, BuyWhere or Lookup.im API?

Both are neck-and-neck — BuyWhere and Lookup.im API each measure 99.02% 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, BuyWhere or Lookup.im API?

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

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

Neither sends browser-friendly CORS headers reliably, so call BuyWhere and Lookup.im 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 Lookup.im API free for commercial use?

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