Finage vs FinFeedAPI

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

Uptime · 30d
Uptime · 90d100%0.0%
Uptime · 30d100%0.0%
P50 · ms574
P95 · ms1122
AuthapiKeyapiKey
CORSyesyes
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, Finage leads on measured uptime — Finage at 100% versus FinFeedAPI at 0.0% 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?

Yes — both Finage and FinFeedAPI send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

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.