GLEIF LEI API vs HOL Registry Broker
Same instrument, two spec sheets — measured, not claimed.
GLEIF LEI API vs HOL Registry Broker: common questions
Which is more reliable, GLEIF LEI API or HOL Registry Broker?
On our scheduled checks, GLEIF LEI API leads on measured uptime — GLEIF LEI API at 100% versus HOL Registry Broker at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, GLEIF LEI API or HOL Registry Broker?
HOL Registry Broker has the lower median latency in our checks — GLEIF LEI API responds in 1052 ms versus HOL Registry Broker at 386 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 HOL Registry Broker need an API key?
GLEIF LEI API needs no key, while HOL Registry Broker requires a free API key. If you want to start calling without signup, reach for GLEIF LEI API first.
Can I call GLEIF LEI API and HOL Registry Broker from the browser?
Only GLEIF LEI API is browser-friendly — it returns CORS headers over HTTPS. HOL Registry Broker needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are GLEIF LEI API and HOL Registry Broker free for commercial use?
GLEIF LEI API has unclear commercial terms, and HOL Registry Broker 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.