shipapis
StarSubmit an APISubmit API

BotsArchive vs Currents

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

APIBotsArchiveNEW—CurrentsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BotsArchive vs Currents: common questions

Which is more reliable, BotsArchive or Currents?

On our scheduled checks, Currents leads on measured uptime — BotsArchive at —% versus Currents at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do BotsArchive and Currents need an API key?

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

Can I call BotsArchive and Currents from the browser?

Only BotsArchive is browser-friendly — it returns CORS headers over HTTPS. Currents needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BotsArchive and Currents free for commercial use?

BotsArchive has unclear commercial terms, and Currents 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.