Finage vs FinFeedAPI

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

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

Finage vs FinFeedAPI: common questions

Which is more reliable, Finage or FinFeedAPI?

On our scheduled checks, FinFeedAPI leads on measured uptime — Finage 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 Finage and FinFeedAPI need an API key?

Both ask you to authenticate — Finage uses an API key and FinFeedAPI uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Finage and FinFeedAPI from the browser?

Only Finage 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 Finage and FinFeedAPI free for commercial use?

Finage 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.