shipapis
StarSubmit an APISubmit API

Registrum API vs Zhipu AI API

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

APIRegistrum APIHEALTHY96Zhipu AI APIHEALTHY87
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms246900
P95 · ms15533308
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

Registrum API vs Zhipu AI API: common questions

Which is more reliable, Registrum API or Zhipu AI API?

Both are neck-and-neck — Registrum API and Zhipu AI 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, Registrum API or Zhipu AI API?

Registrum API has the lower median latency in our checks — Registrum API responds in 246 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 Registrum API and Zhipu AI API need an API key?

Both ask you to authenticate — Registrum 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 Registrum API and Zhipu AI API from the browser?

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

Are Registrum API and Zhipu AI API free for commercial use?

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