shipapis
StarSubmit an APISubmit API

Fake JSON API vs VerifyEd

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

APIFake JSON APIHEALTHY88VerifyEdHEALTHY76
Uptime · 30d
Uptime · 90d99.02%97.1%
Uptime · 30d98.3%95.0%
P50 · ms8651933
P95 · ms20063606
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fake JSON API vs VerifyEd: common questions

Which is more reliable, Fake JSON API or VerifyEd?

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

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

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

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

Are Fake JSON API and VerifyEd free for commercial use?

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