shipapis
StarSubmit an APISubmit API

Invokely vs Lookup.im API

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

APIInvokelyREACHABLE100Lookup.im APIHEALTHY89
Uptime · 30d
Uptime · 90d100%97.8%
Uptime · 30d100%98.3%
P50 · ms227180
P95 · ms2453581
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-10-122026-07-05
operationalpartialdownno data

Invokely vs Lookup.im API: common questions

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

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

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

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

Only Invokely is browser-friendly — it returns CORS headers over HTTPS. Lookup.im API needs a server-side call or proxy, so factor that into which one fits a front-end project.

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

Invokely 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.