Registrum API vs The Guardian

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

Uptime · 30d
Uptime · 90d100%50.6%
Uptime · 30d100%0.0%
P50 · ms138517
P95 · ms15532726
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree developer key — registration required
Rate limitUnpublished5000 calls/day (developer tier)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Registrum API vs The Guardian: common questions

Which is more reliable, Registrum API or The Guardian?

On our scheduled checks, Registrum API leads on measured uptime — Registrum API at 100% versus The Guardian at 50.6% 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, Registrum API or The Guardian?

Registrum API has the lower median latency in our checks — Registrum API responds in 138 ms versus The Guardian at 517 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 The Guardian need an API key?

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

Neither sends browser-friendly CORS headers reliably, so call Registrum API and The Guardian from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Registrum API and The Guardian free for commercial use?

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