Beta
Free public beta. Production-quality verdicts.
The engine is done and the hosted API is open: anonymous, no key, 100 calls a day per IP with a 60/min burst. Every verdict is computed from a pinned IPD-IMGT/HLA release (3.66.0), exactly as it is on a keyed call. It is free: anyone can get a free API key instantly, with 1,000 calls a day, and verified labs can have 10,000 a day by request. See pricing.
Join the list
Hear when early access changes
One email when anything about early access changes, and nothing else. If you want a key now, do not wait for the list: get a free key on its own form. It is issued instantly.
/v1/verify accepts 200,000 characters because typing reports and model output arrive as prose, not because a chart belongs in it. The service does not need names, dates of birth or record numbers to answer, and does not want them. Request content is processed in memory and discarded either way. The privacy policy says exactly what is and is not kept, and the terms of use cover the rest.Rather just write, or have JavaScript off? hello@hlaverify.com reaches the person who built the engine.
What happens to your address
It is stored so we can send you one notice when anything about early access changes. It is never sold, shared or added to a sequence, and you can have it deleted by replying to any mail or writing to hello@hlaverify.com.
The whole record is your address, whatever you typed in the two optional boxes, which form sent it, the time, and the country Cloudflare reports for the connection. Not your IP address. The privacy policy lists it field by field, and the terms of use say what the beta is offered on.
Signing up is not required to use the API. Anonymous access is open right now at 100 calls a day per IP, and the API reference works as a copy-paste starting point. The in-browser demo needs no network call at all.
Today
What already works
Beta describes the commercial packaging, not the answers. The verification engine is the same one that grades the public benchmark, and nothing about a verdict changes when a key is attached to the call.
The full API, no key required
Every endpoint is live at api.hlaverify.com: /v1/verify, /v1/normalize, /v1/allele/{name}, /v1/match and the Lab Toolkit, open at 100 calls a day per IP with no key. See the API reference.
The MCP server, for agents
Point an agent at https://api.hlaverify.com/mcp (Streamable HTTP, nothing to install) and it gets verification as tools. The same tools run locally over stdio from the open-source package.
Production-quality verdicts
No model in the loop, so there is nothing to drift: every answer is computed from the database's own files and is reproducible from the release it names, months later, during an audit.
Pinned to IPD-IMGT/HLA 3.66.0
Every response carries the release that produced it. 47,424 alleles, 793 G groups and 1,580 P groups — and 289 names that were deleted or renamed, with their successors. The pin is the v3.66.0-alpha tag of IPD-IMGT/HLA (2026-10-14), ahead of the latest official release (3.65.0), so names new, renamed or deleted in 3.66.0 differ from the published release; it moves to the official 3.66.0 when IPD-IMGT/HLA publishes it.
Free for anyone
What a key gets
The endpoints are batched, so a key sets two things: how many calls you get a day and how many typings one call may carry. More on pricing.
| Access | Cost | Calls per day | Typings per batch call | Burst |
|---|---|---|---|---|
| No key | Free | 100 per IP | 250 | 60/min |
| Free key instant | Free | 1,000 | 250 | 60/min |
| Verified lab by request | Free | 10,000 | 5,000 | 600/min |
| Enterprise | by agreement | uncapped | 5,000 | uncapped |
Quotas reset at midnight UTC and every response carries the quota left, so a pipeline can throttle before it hits a 429.
Still to come
What the beta does not have yet
- Release pinning per key. There is one IPD-IMGT/HLA release compiled into the service and every caller gets it. Holding a key on an older release is planned, not built. When the pin moves we publish what changed, verdict by verdict.
Larger pilots, self-hosting and OEM terms are on the contact page.
What beta does not mean here
- Not a preview of the answers. The verdicts are final-quality now. If one is wrong it is a bug, and it gets fixed and published like any other.
- Not a data-collection exercise. Request content is processed in memory and discarded, with or without a key. We log counts, not content — see Trust.
- Still not a medical device. It is a research-and-evaluation tool that checks names against a reference database. It supports your validated procedures; it does not replace them.