Fixer API vs Wikipedia REST

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms44898
P95 · ms830961
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree tier — API key requiredUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

Fixer API vs Wikipedia REST: common questions

Which is more reliable, Fixer API or Wikipedia REST?

On our scheduled checks, Wikipedia REST leads on measured uptime — Fixer API at 99.02% versus Wikipedia REST 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, Fixer API or Wikipedia REST?

Wikipedia REST has the lower median latency in our checks — Fixer API responds in 448 ms versus Wikipedia REST at 98 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 Fixer API and Wikipedia REST need an API key?

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

Can I call Fixer API and Wikipedia REST from the browser?

Only Wikipedia REST 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 Fixer API and Wikipedia REST free for commercial use?

Fixer API has unclear commercial terms, and Wikipedia REST allows commercial use on its free tier. 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.