Beta
Free public beta. Production-quality verdicts.
The engine is done and the hosted API is open — anonymous, no key, 60 requests per minute per IP. Every verdict is computed from a pinned IPD-IMGT/HLA release (3.65.0), exactly as it will be when keys are paid for. Paid self-serve keys with higher rate limits arrive within days; join the list to be notified, or email for a beta key now.
Join the list
Tell us where to send the key
One email when self-serve keys go live, and nothing else. If you want a beta key with a higher limit before then, say what for — those are issued by hand, usually the same day.
/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. That is also how beta keys are issued.
What happens to your address
It is stored so we can send you one notice when paid keys go live, plus a beta key if you asked for one. 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 60 requests per minute per IP — the API reference works as a copy-paste starting point, and 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
All four endpoints are live at api.hlaverify.com — /v1/verify, /v1/normalize, /v1/allele/{name} and /v1/match — open at 60 requests per minute per IP. 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.65.0
Every response carries the release that produced it. 46,652 alleles, 784 G groups and 1,563 P groups — and 288 names that were deleted or renamed, with their successors.
Within days
What is coming
- Self-serve paid keys. Checkout on the pricing page, a key in your inbox, no conversation required. Days away, not months.
- Higher rate limits. The 60/min anonymous limit exists to keep the free tier usable for everyone; keyed tiers lift it well past batch-normalizing a LIMS export.
- Per-key usage reporting and release-change notices. Call counts per key — counts, never content — and a heads-up with a diff before a new IPD release becomes the default.
- Release pinning per key. Your key stays on the release you chose until you move it. Available on request during the beta already.
Need a higher limit before that lands? Email for a beta key — they are free during the beta. 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, on the beta exactly as on a paid 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.