shipapis
StarSubmit an APISubmit API

Gladia vs Registrum API

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

APIGladiaHEALTHY76Registrum APIHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1203246
P95 · ms41211553
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Gladia vs Registrum API: common questions

Which is more reliable, Gladia or Registrum API?

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

Registrum API has the lower median latency in our checks — Gladia responds in 1203 ms versus Registrum API at 246 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 Gladia and Registrum API need an API key?

Both ask you to authenticate — Gladia uses an API key and Registrum 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 Gladia and Registrum API from the browser?

Only Gladia 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 Gladia and Registrum API free for commercial use?

Gladia has unclear commercial terms, and Registrum 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.