shipapis
StarSubmit an APISubmit API

Fake JSON API vs RSQ API

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

APIFake JSON APIHEALTHY88RSQ APIHEALTHY91
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms865783
P95 · ms20061387
Authnonenone
CORSyesyes
HTTPSyesno
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 RSQ API: common questions

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

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

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

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

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

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

Are Fake JSON API and RSQ API free for commercial use?

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