Fake JSON API vs Scrapfly

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms8651015
P95 · ms20064809
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fake JSON API vs Scrapfly: common questions

Which is more reliable, Fake JSON API or Scrapfly?

Both are neck-and-neck — Fake JSON API and Scrapfly each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Fake JSON API or Scrapfly?

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

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

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

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

Are Fake JSON API and Scrapfly free for commercial use?

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