ExchangeRate-API (open) vs ValueRay
Same instrument, two spec sheets — measured, not claimed.
ExchangeRate-API (open) vs ValueRay: common questions
Which is more reliable, ExchangeRate-API (open) or ValueRay?
Both are neck-and-neck — ExchangeRate-API (open) and ValueRay each measure 100% 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-API (open) or ValueRay?
ExchangeRate-API (open) has the lower median latency in our checks — ExchangeRate-API (open) responds in 221 ms versus ValueRay at 553 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-API (open) and ValueRay need an API key?
Neither needs a paid key — ExchangeRate-API (open) is callable with no signup, and ValueRay is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call ExchangeRate-API (open) and ValueRay from the browser?
Yes — both ExchangeRate-API (open) and ValueRay 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-API (open) and ValueRay free for commercial use?
ExchangeRate-API (open) has unclear commercial terms, and ValueRay 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.