shipapis
StarSubmit an APISubmit API

Fake JSON API vs GeoNet API

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

APIFake JSON APIHEALTHY88GeoNet APIHEALTHY75
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms8652533
P95 · ms20062808
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fake JSON API vs GeoNet API: common questions

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

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

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

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

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

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

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