shipapis
StarSubmit an APISubmit API

Edgrapi vs Frankfurter

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

APIEdgrapiHEALTHY79FrankfurterHEALTHY86
Uptime · 30d
Uptime · 90d99.02%88.2%
Uptime · 30d100%86.7%
P50 · ms1662370
P95 · ms39974986
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic data (ECB reference rates)
Free tierFree tier — key may be requiredUnlimited — abuse-rate-limited only
Rate limitUnpublishedUnpublished, generous
In directory since2026-07-052026-05-02
operationalpartialdownno data

Edgrapi vs Frankfurter: common questions

Which is more reliable, Edgrapi or Frankfurter?

On our scheduled checks, Edgrapi leads on measured uptime — Edgrapi at 99.02% versus Frankfurter at 88.2% 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 Frankfurter?

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

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

Can I call Edgrapi and Frankfurter from the browser?

Only Frankfurter 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 Frankfurter free for commercial use?

Edgrapi has unclear commercial terms, and Frankfurter allows commercial use on its free tier. 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.