Exchangerate.host vs FinFeedAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Exchangerate.host vs FinFeedAPI: common questions

Which is more reliable, Exchangerate.host or FinFeedAPI?

On our scheduled checks, FinFeedAPI leads on measured uptime — Exchangerate.host at —% versus FinFeedAPI at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Exchangerate.host and FinFeedAPI need an API key?

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

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

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

Are Exchangerate.host and FinFeedAPI free for commercial use?

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