Audexum vs Fake JSON API

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

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

Audexum vs Fake JSON API: common questions

Which is more reliable, Audexum or Fake JSON API?

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

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

Can I call Audexum and Fake JSON API from the browser?

Yes — both Audexum and Fake JSON API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Audexum and Fake JSON API free for commercial use?

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