shipapis
StarSubmit an APISubmit API

Fake JSON API vs HTTPie

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

APIFake JSON APIHEALTHY88HTTPieHEALTHY96
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms865272
P95 · ms20062016
Authnonenone
CORSyesno
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 HTTPie: common questions

Which is more reliable, Fake JSON API or HTTPie?

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

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

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

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

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

Are Fake JSON API and HTTPie free for commercial use?

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