Terms
What you are agreeing to. Stated once, in order.
This is a plain-language summary of the terms the service is offered on, written by the person who operates it. It is not legal advice, and it is not a negotiated contract. If you need one of those, write and we will put a real agreement in front of you.
The service is operated by Brelsford Software LLC. Using HLA-Verify, through the website, the API or the MCP server, means these terms apply to you. Contact: hello@hlaverify.com.
1. The beta
- It is free, and it is a beta. Anonymous access is open at 60 requests per minute per IP with no key. Nothing is charged for it and nothing is owed for it.
- There is no uptime guarantee. No service level, no availability commitment, no support response time. The API may be slow, rate-limited, restarted or unavailable, with or without notice. Do not put it on a path where an outage hurts someone.
- Beta access can change. Limits, endpoints, response shapes and the terms of the free tier can all change while the service is in beta, including the removal of anonymous access. Breaking changes will be announced on this site and to the beta list, but the beta is not a frozen contract.
- Paid tiers are coming. Self-serve keys with higher limits will be sold through the pricing page. Buying one adds the terms shown at checkout; it does not silently change the terms on this page.
- Verdicts are not beta. The answers are computed the same way whether or not a key is attached. If one is wrong it is a bug, and it gets fixed and published like any other.
2. What this is not
HLA-Verify is a research-and-evaluation tool. It is not a medical device and is not offered as one. It has no regulatory clearance, approval or certification, in any jurisdiction, and it is not validated for clinical use.
It verifies nomenclature against a public reference database. It does not perform HLA typing, does not interpret a result, does not determine donor suitability, and does not produce a diagnosis, a treatment recommendation or any clinical determination. Match scores and compatibility output are decision support only: they compute a published rule over the input you supplied, and they assume that input is correct.
Its output supports, and does not replace, clinical judgment and your laboratory's own validated procedures. Responsibility for validating any tool inside an accredited workflow, including this one, stays with your laboratory, exactly as it does for every other tool you use. Do not use HLA-Verify as the sole basis for a clinical decision.
3. Acceptable use
The rules are short because the service is small. Do not:
- Send patient identifiers. Send allele names and typing strings. Not names, dates of birth, medical record numbers or whole charts. See Privacy.
- Work around the rate limits. Rotating IP addresses or keys to get past a limit is not a clever integration, it is the thing the limit exists to stop.
- Resell the service or the reference data. Reselling access, or bulk-extracting the underlying tables to rebuild the database elsewhere, requires a licence. The API answers questions; it is not a distribution channel for IPD-IMGT/HLA.
- Use it commercially under the noncommercial licence. The service code is PolyForm Noncommercial (see below). Commercial use needs a licence, which is the product and is cheerfully sold.
- Attack it. No probing for vulnerabilities without asking first, no attempt to disrupt it for other users. Genuine security reports are welcome at hello@hlaverify.com and will be answered.
Access may be rate-limited, keyed or cut off if usage threatens the service for everyone else. That is an operational decision, not a punishment, and it comes with an email if we can reach you.
4. Reference data and attribution
- The facts come from IPD-IMGT/HLA. Every verdict is computed from a pinned release of the IPD-IMGT/HLA Database, which is published by ANHIG under CC-BY-ND. Cite it: Barker DJ et al., The IPD-IMGT/HLA Database, Nucleic Acids Research, 2025.
- Attribution travels with the answer. Every response carries the source attribution and the release it was computed against, so a verdict you paste into a report brings its citation with it. Keep that attribution when you pass the output on.
- The database is not redistributed. HLA-Verify computes over the release and cites it. It does not republish it, and CC-BY-ND's no-derivatives condition is why bulk table access is not offered.
- Not affiliated. HLA-Verify is not affiliated with, endorsed by, or acting on behalf of ANHIG, IPD-IMGT/HLA, WMDA or NMDP. Their terms for their own data are theirs, and they apply to you as well as to us.
5. Licences on the code
| Component | Licence | What that means |
|---|---|---|
| Engine, benchmark, task generators, graders, harness, adapters | Apache-2.0 | Use it, fork it, build on it, commercially. The evidence has to be checkable to be worth anything. |
| The verification service, hosted and self-hosted | PolyForm Noncommercial 1.0.0 | Read it, evaluate it, use it noncommercially. Commercial use requires a licence: ask. |
| IPD-IMGT/HLA reference data | CC-BY-ND (upstream) | Attributed, cited, never redistributed. |
Output you get back from the API is yours to use. These licences are about the code and the reference database, not about the verdicts you computed with them.
6. No warranty
The service is provided as is, without warranty of any kind, express or implied, including fitness for a particular purpose. That is the ordinary position for a free beta, and it is stated here so nobody has to guess.
It is also the honest position. The engine is deterministic and tested, and a wrong verdict is a bug we want to hear about, but neither of those is a promise that the service is correct for your use, available when you need it, or safe to rely on without your own validation. To the extent the law allows, Brelsford Software LLC is not liable for losses arising from use of the service.
If you need warranties, a service level, indemnities or a signed data agreement, those come with a commercial agreement rather than with the free beta. Ask.
7. Changes and contact
These terms can change while the service is in beta. Material changes are described on this page and sent to the beta list rather than applied quietly. Continuing to use the service after a change means the new terms apply.
Questions about any of the above, including the parts you disagree with: hello@hlaverify.com. Last reviewed September 2026.