shipapis
StarSubmit an APISubmit API

Wikidata vs Zhipu AI API

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

APIWikidataHEALTHY93Zhipu AI APIHEALTHY90
Uptime · 30d
Uptime · 90d100%98.3%
Uptime · 30d100%98.3%
P50 · ms399522
P95 · ms32833308
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Wikidata vs Zhipu AI API: common questions

Which is more reliable, Wikidata or Zhipu AI API?

On our scheduled checks, Wikidata leads on measured uptime — Wikidata at 100% versus Zhipu AI API at 98.3% 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, Wikidata or Zhipu AI API?

Wikidata has the lower median latency in our checks — Wikidata responds in 399 ms versus Zhipu AI API at 522 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 Wikidata and Zhipu AI API need an API key?

Wikidata needs no key, while Zhipu AI API requires a free API key. If you want to start calling without signup, reach for Wikidata first.

Can I call Wikidata and Zhipu AI API from the browser?

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

Are Wikidata and Zhipu AI API free for commercial use?

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