shipapis
StarSubmit an APISubmit API

IPWhois vs Smappee API

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

APIIPWhoisHEALTHY100Smappee APIHEALTHY89
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms23809
P95 · ms5981644
AuthapiKeyapiKey
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs Smappee API: common questions

Which is more reliable, IPWhois or Smappee API?

Both are neck-and-neck — IPWhois and Smappee 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, IPWhois or Smappee API?

IPWhois has the lower median latency in our checks — IPWhois responds in 23 ms versus Smappee API at 809 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 IPWhois and Smappee API need an API key?

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

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

Are IPWhois and Smappee API free for commercial use?

IPWhois has unclear commercial terms, and Smappee 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.