DummyJSON vs Logotypes

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

Uptime · 30d
Uptime · 90d100%47.8%
Uptime · 30d100%0.0%
P50 · ms913645
P95 · ms19294993
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 Logotypes: common questions

Which is more reliable, DummyJSON or Logotypes?

On our scheduled checks, DummyJSON leads on measured uptime — DummyJSON at 100% versus Logotypes at 47.8% 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, DummyJSON or Logotypes?

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

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

Can I call DummyJSON and Logotypes from the browser?

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

Are DummyJSON and Logotypes free for commercial use?

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