Finage vs TaxID

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

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

Finage vs TaxID: common questions

Which is more reliable, Finage or TaxID?

Both are neck-and-neck — Finage and TaxID each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Finage or TaxID?

Finage has the lower median latency in our checks — Finage responds in 574 ms versus TaxID at 729 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 Finage and TaxID need an API key?

Both ask you to authenticate — Finage uses an API key and TaxID 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 TaxID from the browser?

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

Are Finage and TaxID free for commercial use?

Finage has unclear commercial terms, and TaxID 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.