Registrum API vs Warnely

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

Uptime · 30d
Uptime · 90d100%90.2%
Uptime · 30d100%83.3%
P50 · ms246334
P95 · ms15531375
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Registrum API vs Warnely: common questions

Which is more reliable, Registrum API or Warnely?

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

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

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

Can I call Registrum API and Warnely from the browser?

Neither sends browser-friendly CORS headers reliably, so call Registrum API and Warnely 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 Warnely free for commercial use?

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