shipapis
StarSubmit an APISubmit API

Apify vs GLEIF LEI API

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

APIApifyHEALTHY96GLEIF LEI APIHEALTHY65
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3811052
P95 · ms7652472
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apify vs GLEIF LEI API: common questions

Which is more reliable, Apify or GLEIF LEI API?

Both are neck-and-neck — Apify and GLEIF LEI API 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, Apify or GLEIF LEI API?

Apify has the lower median latency in our checks — Apify responds in 381 ms versus GLEIF LEI API at 1052 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 Apify and GLEIF LEI API need an API key?

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

Can I call Apify and GLEIF LEI API from the browser?

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

Are Apify and GLEIF LEI API free for commercial use?

Apify has unclear commercial terms, and GLEIF LEI API 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.