shipapis
StarSubmit an APISubmit API

Lookup.im API vs Zhipu AI API

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

APILookup.im APIHEALTHY84Zhipu AI APIHEALTHY87
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms1158900
P95 · ms35813308
AuthapiKeyapiKey
CORSnoyes
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 Zhipu AI API: common questions

Which is more reliable, Lookup.im API or Zhipu AI API?

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

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

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

Only Zhipu AI API 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 Lookup.im API and Zhipu AI API free for commercial use?

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