shipapis
StarSubmit an APISubmit API

Registrum API vs Shields

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

APIRegistrum APINEW—ShieldsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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?

On our scheduled checks, Shields leads on measured uptime — Registrum API at —% versus Shields at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

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.