shipapis
StarSubmit an APISubmit API

Fake JSON API vs NetworkCalc

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

APIFake JSON APIHEALTHY88NetworkCalcHEALTHY91
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms865448
P95 · ms20063976
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree public API, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fake JSON API vs NetworkCalc: common questions

Which is more reliable, Fake JSON API or NetworkCalc?

Both are neck-and-neck — Fake JSON API and NetworkCalc 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 NetworkCalc?

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

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

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

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

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