Free public beta: the API is open at 100 calls a day per IP, no key. Paid tiers start at $49/mo, set up by email: see pricing.
HLA-Verify

Research

Research access is free with approval

If you are checking HLA nomenclature for academic or nonprofit research, a key costs nothing. It is approved by hand rather than bought, because the point is to know who is using it and for what, not to collect money from a graduate student harmonising a cohort.

Apply by email See the paid tiers

What qualifies

  • Academic, hospital and nonprofit research. Cohort harmonisation, registry analysis, population genetics, method development, a thesis.
  • Teaching. A course or workshop that needs the API live in front of a room.
  • Model evaluation and benchmarking. Running HLA-Bench or your own suite against the API, including reproducing published results.
  • Open-source tooling. A library or pipeline that calls the API, as long as what you ship is not sold.

What does not qualify is commercial use: a clinical service billing for results, a product with the verification inside it, or a vendor evaluating it for a product. That is what the paid tiers are for, and Starter starts at $49 a month.

What you get

  • A key with limits set to the work. Tell us the volume you expect and the key is sized for it. Most research sits inside the Lab tier's shape; a one-off bulk harmonisation of a large cohort is fine and is easier to plan if you say so up front.
  • The same engine and the same release as every paying caller. There is no reduced-accuracy research mode. Every response names the IPD-IMGT/HLA release it was computed against, which is what makes a result reproducible at review time.
  • The same data handling. Request content is processed in memory and discarded. See privacy for what is and is not kept.

What we ask in return

  • Cite the reference database. IPD-IMGT/HLA (Barker DJ et al., Nucleic Acids Research 2025). Citing HLA-Verify as well is welcome, not required.
  • Name the release. If a result depends on nomenclature, put the release version in the methods. Every response carries it.
  • Tell us when something is wrong. A disagreement with the database is a bug and gets fixed and published. Research users find the interesting ones.

How to apply

One email to hello@hlaverify.com. It reaches the person who built the engine, and there is no form and no sales sequence behind it.

Say four things: who you are and where, what you are studying, roughly how many typings or calls you expect, and whether any of it is commercial. That is enough to approve most requests the same day. If the answer is no it will say why, and the free public beta stays open either way at 100 calls a day with no key.

Send allele names and typing strings, not patient identifiers. The service does not need names, dates of birth or record numbers to answer, and does not want them. De-identifying before you call is the caller's responsibility. The privacy policy says exactly what is and is not kept, and the terms of use cover the rest.
Apply for research access Read the API reference HLA-Bench results