BotsArchive vs Registrum API

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

Uptime · 30d
Uptime · 90d97.1%100%
Uptime · 30d95.0%100%
P50 · ms790246
P95 · ms44481553
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BotsArchive vs Registrum API: common questions

Which is more reliable, BotsArchive or Registrum API?

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

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

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

Can I call BotsArchive and Registrum API from the browser?

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

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