GLEIF LEI API vs OkSurf

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

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

GLEIF LEI API vs OkSurf: common questions

Which is more reliable, GLEIF LEI API or OkSurf?

On our scheduled checks, OkSurf leads on measured uptime — GLEIF LEI API at —% versus OkSurf 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 GLEIF LEI API and OkSurf need an API key?

Neither needs a paid key — GLEIF LEI API is callable with no signup, and OkSurf is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

Are GLEIF LEI API and OkSurf free for commercial use?

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