GLEIF LEI API vs OkSurf
Same instrument, two spec sheets — measured, not claimed.
GLEIF LEI API vs OkSurf: common questions
Which is more reliable, GLEIF LEI API or OkSurf?
Both are neck-and-neck — GLEIF LEI API and OkSurf 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, GLEIF LEI API or OkSurf?
OkSurf has the lower median latency in our checks — GLEIF LEI API responds in 1052 ms versus OkSurf at 624 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 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.