Install Jentic One Beta

Connect the Labgnostic EQA Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Labgnostic EQA Public API, 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%2Flabgnostic.com%2Flabgnostic" | 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%2Flabgnostic.com%2Flabgnostic" | 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 Labgnostic EQA Public API.

Create or update an EQA programme by programmeCode with a name and description

Replace a programme's analytes with name, code, codingSystem, and accepted units, or use the multicode form with Quantitative or Qualitative type and several analyteCodes

Upsert an assessment event with startDate, endDate, and challenges that list specimens by typeCode and the analyte codes each specimen is tested for

Upsert many assessment events for a programme in a single request

GET STARTED

Start building with Labgnostic EQA Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Labgnostic EQA Public API for, with concrete tasks.

★ Programme and Analyte Setup

An EQA provider launching a new scheme creates the programme by its programmeCode, checks the global units-of-measure list, and then sets the programme's analytes with their codes, coding systems, and the units labs may report in. The multicode variant lets one analyte carry several codes with a Quantitative or Qualitative type, which suits schemes that accept results under more than one coding system.

Call PUT /programmes/{programmeCode} with programmeCode 'CHEM-01' and name 'General Chemistry', GET /globals/units-of-measure, then PUT /programmes/{programmeCode}/analytes with analytes for glucose and creatinine and their units

Scheduling Assessment Events

Each round of an EQA scheme is an assessment event. The agent upserts an event by assessmentEventCode with startDate and endDate and a set of challenges, where each challenge has a unique code and lists specimens by typeCode with the programme analytes they are tested for. A whole year of rounds can be sent in one batch upsert.

Call PUT /programmes/{programmeCode}/assessment-events/{assessmentEventCode} for 'CHEM-01-2026-Q1' with startDate '2026-01-12', endDate '2026-01-30', and one challenge with code 'A' and a serum specimen testing glucose

Round Calendar Review

Before sending specimens, a coordinator agent lists the programme's assessment events within a start-date window, pages through the results, and reads any single event to confirm its challenges and dates. Events created in error can be deleted by programme and event code.

Call GET /programmes/{programmeCode}/assessment-events with minStartDateTime '2026-01-01T00:00:00Z' and maxStartDateTime '2026-03-31T23:59:59Z', then GET the first event by its assessmentEventCode

AI Agent EQA Administration via Jentic

An AI agent maintains Labgnostic programmes through Jentic without handling the JWT itself. It searches by intent, receives the matching programme, analyte, or assessment-event operation with its input schema, and executes with the bearer token injected at run time, so updating a scheme's rounds becomes one step in a larger lab-operations workflow.

Search Jentic for 'schedule an EQA assessment event', load the UpsertAssessmentEventEndpoint schema, and execute it with the programmeCode, assessmentEventCode, dates, and challenges

Key Endpoints

11 endpoints — the labgnostic eqa public api sets up external quality assessment programmes for clinical laboratories on the labgnostic platform.

METHOD

PATH

DESCRIPTION

PUT

/programmes/{programmeCode}

Create or update a programme

GET

/programmes/{programmeCode}

Get a programme

PUT

/programmes/{programmeCode}/analytes

Update programme analytes

PUT

/programmes/{programmeCode}/assessment-events/{assessmentEventCode}

Create or update an assessment event

PUT

/programmes/{programmeCode}/assessment-events

Upsert many assessment events

GET

/programmes/{programmeCode}/assessment-events

List assessment events

GET

/globals/units-of-measure

List units of measure

PUT

/programmes/{programmeCode}

Create or update a programme

GET

/programmes/{programmeCode}

Get a programme

PUT

/programmes/{programmeCode}/analytes

Update programme analytes

PUT

/programmes/{programmeCode}/assessment-events/{assessmentEventCode}

Create or update an assessment event

PUT

/programmes/{programmeCode}/assessment-events

Upsert many assessment events

GET

/programmes/{programmeCode}/assessment-events

List assessment events

GET

/globals/units-of-measure

List units of measure

Why Jentic?

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

Setup

Wiring the Labgnostic EQA Public API by hand means obtaining and attaching a JWT bearer token and building the nested challenge, specimen, and analyte payloads for each upsert. Through Jentic you install once, import Labgnostic from the API Directory, store the token once, and your agent calls it.

Permission scoping

Labgnostic puts the programme code in the URL path (/programmes/{programmeCode}/...), so a rule can pin your agent to one programme and the operations you pick. You choose that set, so destructive ones like assessment event deletion or analyte replacement are not included unless you add them.

Credential isolation

Your Labgnostic token 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 'schedule an EQA assessment event' or 'set programme analytes', and Jentic returns the matching Labgnostic operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Labgnostic EQA Public API through Jentic.

What authentication does the Labgnostic EQA Public API use?

Per its OpenAPI spec, the Labgnostic EQA Public API uses the JWTBearerAuth scheme: a JWT sent as a bearer token in the Authorization header. The spec does not describe how the token is issued, so obtain it from Labgnostic for your provider account. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time.

Can I define analytes with more than one code using the Labgnostic EQA Public API?

Yes. PUT /programmes/{programmeCode}/analytes/multicode takes analytes with a name, a type of Quantitative or Qualitative, and an analyteCodes list where each entry has its own code, codingSystem, and unit. The simpler PUT /programmes/{programmeCode}/analytes form takes one code, codingSystem, and a units list per analyte.

What are the rate limits for the Labgnostic EQA Public API?

The OpenAPI spec does not specify rate limits. Check the published definition at https://app.swaggerhub.com/apis/MSPATIL/labgnostic-eqa-public-api/v1 or contact Labgnostic for the limits on your account.

How do I schedule an assessment event through Jentic with the Labgnostic EQA Public API?

Search Jentic for 'schedule an EQA assessment event' and it returns the UpsertAssessmentEventEndpoint operation with its input schema. Execute PUT /programmes/{programmeCode}/assessment-events/{assessmentEventCode} with challenges (required), plus startDate and endDate. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Labgnostic MCP server?

You don't need an MCP server to give your agent the Labgnostic EQA Public API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered by intent on demand, so no extra tool definitions are loaded into the agent's context.

Can I limit what my agent is allowed to do with the Labgnostic EQA Public API?

Yes. Write a rule that allows only the GET and PUT assessment-event operations under one programmeCode, and the agent can schedule and review rounds for that scheme while other programmes, their analytes, and event deletion stay out of reach. Every call runs through your own instance and is logged.

Labgnostic EQA Public API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Community OpenAPI document · agent-readyHealthcareClinical Databearer11 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and update Labgnostic EQA programmes, configure the analytes they test, and schedule or remove assessment events with their challenges and specimens.

Use for: Create a new haematology EQA programme, Add glucose and HbA1c as analytes on this programme, Schedule the next assessment event with two challenges, List all assessment events starting this quarter

Not supported: Does not handle patient records, lab result submission by participating labs, or specimen shipping. Use for configuring EQA programmes, their analytes, and assessment events only.

The Labgnostic EQA Public API sets up external quality assessment programmes for clinical laboratories on the Labgnostic platform. A provider creates or updates a programme by its programmeCode, defines the analytes it tests with their codes, coding systems, and accepted units, and schedules assessment events whose challenges list the specimens and analytes labs must test. Events can be upserted one at a time or in batches, listed by start date with paging, and deleted, and a global units-of-measure list supplies the valid units for analyte setup.

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).

60%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

48%

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: C-Signals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

56%

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: A-Signals: 1

75%

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: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Labgnostic EQA Public API to your agent

Capabilities

Start building with Labgnostic EQA Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Labgnostic EQA Public API

Jentic AI Readiness Score

Labgnostic EQA Public API

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