shipapis
StarSubmit an APISubmit API

Fake JSON API vs Scrnify

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

APIFake JSON APINEW—ScrnifyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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 Scrnify: common questions

Which is more reliable, Fake JSON API or Scrnify?

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

Fake JSON API needs no key, while Scrnify 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 Scrnify from the browser?

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

Are Fake JSON API and Scrnify free for commercial use?

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