shipapis
StarSubmit an APISubmit API

Fake JSON API vs Httpbin

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

APIFake JSON APIHEALTHY88HttpbinHEALTHY68
Uptime · 30d
Uptime · 90d99.02%66.7%
Uptime · 30d98.3%65.0%
P50 · ms865785
P95 · ms20062559
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fake JSON API vs Httpbin: common questions

Which is more reliable, Fake JSON API or Httpbin?

On our scheduled checks, Fake JSON API leads on measured uptime — Fake JSON API at 99.02% versus Httpbin at 66.7% 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, Fake JSON API or Httpbin?

Httpbin has the lower median latency in our checks — Fake JSON API responds in 865 ms versus Httpbin at 785 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 Fake JSON API and Httpbin need an API key?

Neither needs a paid key — Fake JSON API is callable with no signup, and Httpbin is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

Yes — both Fake JSON API and Httpbin 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 Fake JSON API and Httpbin free for commercial use?

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