shipapis
StarSubmit an APISubmit API

DummyJSON vs Spoo.me

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

APIDummyJSONHEALTHY100Spoo.meHEALTHY97
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms91231
P95 · ms19291286
Authnonenone
CORSyesno
HTTPSyesyes
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 Spoo.me: common questions

Which is more reliable, DummyJSON or Spoo.me?

Both are neck-and-neck — DummyJSON and Spoo.me each measure 100% 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, DummyJSON or Spoo.me?

DummyJSON has the lower median latency in our checks — DummyJSON responds in 91 ms versus Spoo.me at 231 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 DummyJSON and Spoo.me need an API key?

Neither needs a paid key — DummyJSON is callable with no signup, and Spoo.me is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call DummyJSON and Spoo.me from the browser?

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

Are DummyJSON and Spoo.me free for commercial use?

DummyJSON has unclear commercial terms, and Spoo.me 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.