Exchangerate.host vs Markbase
Same instrument, two spec sheets — measured, not claimed.
Exchangerate.host vs Markbase: common questions
Which is more reliable, Exchangerate.host or Markbase?
Both are neck-and-neck — Exchangerate.host 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, Exchangerate.host or Markbase?
Exchangerate.host has the lower median latency in our checks — Exchangerate.host responds in 398 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 Exchangerate.host and Markbase need an API key?
Neither needs a paid key — Exchangerate.host is callable with no signup, and Markbase is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Exchangerate.host and Markbase from the browser?
Yes — both Exchangerate.host 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 Exchangerate.host and Markbase free for commercial use?
Exchangerate.host 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.