Get in touch
One address, answered by the person who built it
The API itself needs no conversation: it is in free public beta, open at 100 calls a day per IP with no key. It is free: anyone can get a free key instantly (1,000 calls a day), and verified labs can have 10,000 a day by request (see pricing). This page is for everything a form cannot handle: pilots, self-hosting, OEM terms, evaluation work. Email is the fastest path, and there is no sales sequence waiting on the other end of it.
What to say
Any of these gets a real answer. Mentioning which one you are saves a round trip.
Pilot access for a laboratory
Tell us roughly how many typings a month, whether you need the release pinned to something specific, and whether data may leave your network. We will come back with a key or a container, and a scope for the pilot.
Ten labs can join the Founding Lab programme: a free Lab-tier key during early access and a direct line to the person who built the engine.
OEM / embedding it in a product
If you are a LIMS, diagnostics or AI product vendor putting model output in front of laboratories, say what the surface is and where verification would sit. Commercial licensing of the service code is straightforward.
Evaluate a model on HLA-Bench
Sealed-split runs with a versioned report, custom task families, or an export to verifiers, Inspect AI or Harbor. Tell us the model endpoint and what you want measured.
Security, data handling or licensing
Most of it is already written down on the Trust page — data handling, reference-data licensing, reproducibility, regulatory scope, code licences. If something is missing or your reviewer needs it in another form, ask.
Before you write
- The benchmark is already public. If you want to judge whether this is worth a conversation, the numbers and the grading code are the honest place to start.
- The API is fully documented. Request and response shapes are on the reference page, generated from real engine output — you can evaluate the integration before asking for a key.
- Self-hosting is a supported answer. If "can data leave the network" is a blocker, it is not a blocker. Say so and we will start from the container.