shipapis
StarSubmit an APISubmit API

DummyJSON vs RSQ API

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

APIDummyJSONNEW—RSQ APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limit100 req/window · 99 remaining · resets 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs RSQ API: common questions

Which is more reliable, DummyJSON or RSQ API?

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

Neither needs a paid key — DummyJSON 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 DummyJSON and RSQ API from the browser?

Only DummyJSON 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 DummyJSON and RSQ API free for commercial use?

DummyJSON 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.