Exchangerate.dev vs Markbase
Same instrument, two spec sheets — measured, not claimed.
Exchangerate.dev vs Markbase: common questions
Which is more reliable, Exchangerate.dev or Markbase?
On our scheduled checks, Markbase leads on measured uptime — Exchangerate.dev at 71.6% versus Markbase 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, Exchangerate.dev or Markbase?
Exchangerate.dev has the lower median latency in our checks — Exchangerate.dev responds in 336 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.dev and Markbase need an API key?
Neither needs a paid key — Exchangerate.dev 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.dev and Markbase from the browser?
Yes — both Exchangerate.dev 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.dev and Markbase free for commercial use?
Exchangerate.dev 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.