Audexum vs Hunter

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

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

Audexum vs Hunter: common questions

Which is more reliable, Audexum or Hunter?

On our scheduled checks, Hunter leads on measured uptime — Audexum at —% versus Hunter 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 Audexum and Hunter need an API key?

Both ask you to authenticate — Audexum uses an API key and Hunter uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Audexum and Hunter from the browser?

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

Are Audexum and Hunter free for commercial use?

Audexum has unclear commercial terms, and Hunter 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.