Archive.org vs Fixer API

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

Uptime · 30d
Uptime · 90d97.1%99.02%
Uptime · 30d96.7%98.3%
P50 · ms813448
P95 · ms2764830
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (rights vary per item)Unverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Archive.org vs Fixer API: common questions

Which is more reliable, Archive.org or Fixer API?

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

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

Archive.org needs no key, while Fixer API requires a free API key. If you want to start calling without signup, reach for Archive.org first.

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

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

Are Archive.org and Fixer API free for commercial use?

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