Install Jentic One Beta

Connect the HLA-Verify to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HLA-Verify, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhlaverify.com%2Fhlaverify" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhlaverify.com%2Fhlaverify" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with HLA-Verify API.

Classify every allele-shaped token in HLA report text or model output

Normalize reported HLA typings to the current IPD-IMGT/HLA release

Look up facts for one allele, prefix, group, or deleted name

Return a donor-recipient match verdict using rules R1 through R6

QC-check an HLA typing across all loci for resolution and renames

GET STARTED

Start building with HLA-Verify API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HLA-Verify API for, with concrete tasks.

★ HLA Typing QC

Quality-check an HLA typing before it enters a report so stale names and resolution errors are caught against the current release. The API checks a typing across all loci and flags renames, locus mismatches, and resolution issues deterministically. Histocompatibility labs use this as an automated QC step that does not depend on a model or stored data.

POST /v1/typing/check with the typing string and review the resolution and locus-mismatch findings it returns.

Donor-Recipient Match Verification

Confirm a donor-recipient HLA match using explicit rules rather than hand arithmetic, so the verdict is reproducible. The API returns a match verdict under rules R1 through R6 and a separate immunogenetic compatibility assessment. Transplant workflows use this to double-check match calls before they are acted on.

POST /v1/match with the donor and recipient typings and return the R1 through R6 verdict.

Report Text Nomenclature Validation

Scan free text or model output for HLA allele names and bring any reported typings up to the current release. The API classifies each allele-shaped token in the text and normalizes reported typings deterministically. Teams use this to validate HLA names in documents without sending any patient identifiers.

POST /v1/verify with the report text to classify allele tokens, then POST /v1/normalize to bring reported typings to the current release.

Agent-Assisted Nomenclature Check

An AI agent validates the HLA names in generated or transcribed output before a human relies on them, flagging deleted or renamed alleles. Through Jentic the agent discovers the verify and normalize operations, loads their schemas, and runs them without storing any input. This lets a clinical-writing assistant self-check HLA nomenclature on the fly.

Search Jentic for 'validate HLA typing', call POST /v1/verify on the model output, and flag any token the response marks as deleted or renamed.

Key Endpoints

15 endpoints — the hla-verify api validates hla nomenclature and checks donor-recipient match arithmetic against a pinned ipd-imgt/hla release.

METHOD

PATH

DESCRIPTION

POST

/v1/verify

Classify allele-shaped tokens in report text or model output

POST

/v1/normalize

Normalize reported typings to the current release

GET

/v1/allele/{name}

Facts for one allele, prefix, group, or deleted name

POST

/v1/match

Donor-recipient match verdict (rules R1 to R6)

POST

/v1/typing/check

QC-check one HLA typing across all loci

POST

/v1/compat

Donor and recipient immunogenetic compatibility

POST

/v1/glstring

Validate and normalize a GL String

POST

/v1/verify

Classify allele-shaped tokens in report text or model output

POST

/v1/normalize

Normalize reported typings to the current release

GET

/v1/allele/{name}

Facts for one allele, prefix, group, or deleted name

POST

/v1/match

Donor-recipient match verdict (rules R1 to R6)

POST

/v1/typing/check

QC-check one HLA typing across all loci

POST

/v1/compat

Donor and recipient immunogenetic compatibility

POST

/v1/glstring

Validate and normalize a GL String

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HLA-Verify by hand means attaching the X-API-Key header and chaining the verify, normalize, and match calls while keeping patient identifiers out of every request. Through Jentic you install once, import HLA-Verify from the API Directory, store the key once, and your agent calls the validation operations.

Permission scoping

HLA-Verify carries the typings, GL Strings, and report text inside the request body, so a rule bounds which operations your agent may call rather than which record. You can allow just the verify, normalize, and match operations and keep the checkout and billing endpoints out of the agent's reach.

Credential isolation

Your HLA-Verify API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'validate HLA typing' or 'check a donor match', and Jentic returns the matching HLA-Verify operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using HLA-Verify API through Jentic.

Is there an HLA-Verify MCP server?

Yes. HLA-Verify exposes a remote MCP endpoint over streamable HTTP. You can also connect HLA-Verify directly through Jentic: your agent gets the full 15-endpoint surface without loading another server's tool definitions into its context, your API key is injected at call time by your self-hosted instance, and your own rules decide which operations the agent may call.

What authentication does HLA-Verify use?

HLA-Verify authenticates with an API key in the X-API-Key header, per its OpenAPI spec, and some endpoints are also reachable without a key during the public beta. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I verify a donor-recipient match with HLA-Verify?

Yes. POST /v1/match returns a donor-recipient match verdict under rules R1 through R6, and POST /v1/compat assesses immunogenetic compatibility including the HLA-B leader. Both run deterministically and store nothing from the request.

What are the rate limits for HLA-Verify?

The OpenAPI spec does not publish numeric rate limits; HLA-Verify lists its published prices and limits on its pricing endpoint. See the HLA-Verify pricing page at https://hlaverify.com/pricing for the current limits that apply to your tier.

How do I validate an HLA typing through Jentic?

Search Jentic with the query 'validate HLA typing', load the schema for POST /v1/typing/check, and execute it with the typing string to get resolution and rename findings. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with HLA-Verify?

Yes. Write a rule that allows only the read and validation operations you need, such as POST /v1/verify and POST /v1/typing/check, so the agent can check nomenclature but cannot start a checkout or touch billing endpoints, and every call it makes is logged. Because the service stores nothing and refuses patient identifiers, the agent only ever handles the de-identified tokens you pass.

HLA-Verify

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareClinical DataapiKey15 EndpointsREST

For Agents

Validate HLA alleles and typings, normalize them to the current IPD-IMGT/HLA release, score donor-recipient matches, and check GL Strings, deterministically and without storing data.

Use for: Validate the HLA alleles mentioned in this report text, Normalize these typings to the current HLA release, Get the facts for a specific HLA allele, Check the donor-recipient match verdict for this pair

Not supported: Does not store data, diagnose patients, or accept patient identifiers. Use for HLA nomenclature validation and donor-recipient match arithmetic only.

The HLA-Verify API validates HLA nomenclature and checks donor-recipient match arithmetic against a pinned IPD-IMGT/HLA release. It classifies allele-shaped tokens in report text, normalizes reported typings to the current release, returns donor-recipient match verdicts under rules R1 through R6, assesses immunogenetic compatibility, and validates GL Strings. It is deterministic and stores nothing, and it neither needs nor accepts patient identifiers, so callers de-identify before sending.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

48%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HLA-Verify to your agent

Capabilities

Start building with HLA-Verify API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

HLA-Verify

Jentic AI Readiness Score

HLA-Verify

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness