Edgrapi vs Exchangerate.host

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms1662398
P95 · ms39973637
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Edgrapi vs Exchangerate.host: common questions

Which is more reliable, Edgrapi or Exchangerate.host?

Both are neck-and-neck — Edgrapi and Exchangerate.host 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, Edgrapi or Exchangerate.host?

Exchangerate.host has the lower median latency in our checks — Edgrapi responds in 1662 ms versus Exchangerate.host at 398 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 Edgrapi and Exchangerate.host need an API key?

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

Can I call Edgrapi and Exchangerate.host from the browser?

Only Exchangerate.host is browser-friendly — it returns CORS headers over HTTPS. Edgrapi needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Edgrapi and Exchangerate.host free for commercial use?

Edgrapi has unclear commercial terms, and Exchangerate.host 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.