Fixer vs Markbase

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms481866
P95 · ms45841568
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783519324
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fixer vs Markbase: common questions

Which is more reliable, Fixer or Markbase?

Both are neck-and-neck — Fixer and Markbase each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Fixer or Markbase?

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

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

Can I call Fixer and Markbase from the browser?

Yes — both Fixer and Markbase 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 Fixer and Markbase free for commercial use?

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