ddownload vs Fake JSON API

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms365865
P95 · ms7922006
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ddownload vs Fake JSON API: common questions

Which is more reliable, ddownload or Fake JSON API?

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

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

Fake JSON API needs no key, while ddownload requires a free API key. If you want to start calling without signup, reach for Fake JSON API first.

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

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

Are ddownload and Fake JSON API free for commercial use?

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