Registrum API vs Voidly

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

Uptime · 30d
Uptime · 90d100%86.0%
Uptime · 30d100%81.0%
P50 · ms1381865
P95 · ms15534655
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree tier — API key requiredFree (keyless data endpoints; Hydra ML endpoints need a key)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Registrum API vs Voidly: common questions

Which is more reliable, Registrum API or Voidly?

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

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

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

Can I call Registrum API and Voidly from the browser?

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

Registrum API has unclear commercial terms, and Voidly allows commercial use on its free tier. 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.