shipapis
StarSubmit an APISubmit API

Lookup.im API vs SnapshotAPI

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

APILookup.im APIHEALTHY84SnapshotAPIDEAD0
Uptime · 30d
Uptime · 90d99.02%6.9%
Uptime · 30d100%0.0%
P50 · ms1158396
P95 · ms3581547
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lookup.im API vs SnapshotAPI: common questions

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

On our scheduled checks, Lookup.im API leads on measured uptime — Lookup.im API at 99.02% versus SnapshotAPI at 6.9% 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, Lookup.im API or SnapshotAPI?

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

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

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

Are Lookup.im API and SnapshotAPI free for commercial use?

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