shipapis
StarSubmit an APISubmit API

Abstract API vs Fake JSON API

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

APIAbstract APIHEALTHY93Fake JSON APIHEALTHY92
Uptime · 30d
Uptime · 90d98.3%99.44%
Uptime · 30d98.3%100%
P50 · ms391342
P95 · ms16562056
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Abstract API vs Fake JSON API: common questions

Which is more reliable, Abstract API or Fake JSON API?

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

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

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

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

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

Abstract API 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.