Archive.org vs Free Dictionary API

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

Uptime · 30d
Uptime · 90d97.1%100%
Uptime · 30d96.7%100%
P50 · ms813674
P95 · ms27642196
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (rights vary per item)Unverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Archive.org vs Free Dictionary API: common questions

Which is more reliable, Archive.org or Free Dictionary API?

On our scheduled checks, Free Dictionary API leads on measured uptime — Archive.org at 97.1% versus Free Dictionary 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, Archive.org or Free Dictionary API?

Free Dictionary API has the lower median latency in our checks — Archive.org responds in 813 ms versus Free Dictionary API at 674 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 Archive.org and Free Dictionary API need an API key?

Neither needs a paid key — Archive.org is callable with no signup, and Free Dictionary API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Archive.org and Free Dictionary API from the browser?

Yes — both Archive.org and Free Dictionary API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Archive.org and Free Dictionary API free for commercial use?

Archive.org has unclear commercial terms, and Free Dictionary 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.