Noozra vs Registrum API

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

Uptime · 30d
Uptime · 90d80.9%100%
Uptime · 30d41.4%100%
P50 · ms289138
P95 · ms9451553
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (aggregated RSS headlines)Unverified
Free tierFree tier available (pricing tiers published at /api/pricing)Free tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Noozra vs Registrum API: common questions

Which is more reliable, Noozra or Registrum API?

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

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

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

Can I call Noozra and Registrum API from the browser?

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

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