Edgrapi vs ExchangeRate-API (open)

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms1662221
P95 · ms39971091
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-API (open): common questions

Which is more reliable, Edgrapi or ExchangeRate-API (open)?

On our scheduled checks, ExchangeRate-API (open) leads on measured uptime — Edgrapi at 99.02% versus ExchangeRate-API (open) at 100% 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, Edgrapi or ExchangeRate-API (open)?

ExchangeRate-API (open) has the lower median latency in our checks — Edgrapi responds in 1662 ms versus ExchangeRate-API (open) at 221 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-API (open) need an API key?

ExchangeRate-API (open) needs no key, while Edgrapi requires a free API key. If you want to start calling without signup, reach for ExchangeRate-API (open) first.

Can I call Edgrapi and ExchangeRate-API (open) from the browser?

Only ExchangeRate-API (open) 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-API (open) free for commercial use?

Edgrapi has unclear commercial terms, and ExchangeRate-API (open) 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.