shipapis
StarSubmit an APISubmit API

Registrum API vs Shields

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

APIRegistrum APIHEALTHY96ShieldsHEALTHY100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms24630
P95 · ms1553925
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Registrum API vs Shields: common questions

Which is more reliable, Registrum API or Shields?

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

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

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

Can I call Registrum API and Shields from the browser?

Only Shields 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 Shields free for commercial use?

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