Infermedica API

Name: Infermedica API API
Brand: Infermedica API
Availability: InStock

✓ Official Vendor SpecHealthcareClinical DataapiKey16 EndpointsREST

For Agents

Run adaptive symptom-check interviews, get triage recommendations, parse free-text symptoms into coded concepts, and look up clinical concepts (symptoms, conditions, risk factors, lab tests).

Connect the Infermedica API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Infermedica 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Infermedica API API.

Run an adaptive diagnostic interview where each call to /diagnosis returns either the next clarifying question or a ranked condition list

Recommend a triage level — self-care, consultation, or emergency — for a given symptom set via /triage

Parse free-text patient narratives into structured Infermedica concept IDs via /parse

Suggest related symptoms a patient might also have via /suggest, improving interview completeness

GET STARTED

Start building with Infermedica API API

Explore with Jentic

View OpenAPI Document

Infermedica is an AI-powered clinical decision support API for symptom checking, differential diagnosis, and patient triage. The 16-endpoint v3 API runs adaptive diagnostic interviews via /diagnosis, recommends triage levels (emergency, consultation, self-care) via /triage, parses free-text patient complaints into coded symptoms via /parse, and exposes structured medical concept catalogues for symptoms, conditions, risk factors, and lab tests. Authentication uses a paired App-Id and App-Key header credential model, allowing partners to track usage per integration.

Use Cases

Patterns agents use Infermedica API API for, with concrete tasks.

★ Patient-Facing Symptom Checker

Power a symptom-checker chatbot or web app where a patient describes how they feel and the application asks adaptive follow-up questions before showing likely conditions and a triage recommendation. Each turn calls POST /diagnosis with the running evidence list; Infermedica returns either the next question or a stop signal with the differential. POST /triage returns the recommended care level.

Call POST /diagnosis with sex='female', age=35, and an evidence array containing symptom 's_21' (abdominal pain), then return the next recommended question.

Free-Text Intake Parsing

When a patient types 'I've had a headache and nausea for two days', POST /parse converts that to Infermedica concept IDs (e.g., s_98 for headache, s_156 for nausea), so a downstream /diagnosis call has structured evidence. Useful for chat-based intake flows and EHR free-text fields where humans describe symptoms in natural language.

POST /parse with text 'severe headache and nausea since yesterday' and return the extracted Infermedica concept IDs.

Emergency Triage Pre-Check

Before running a full diagnostic interview, POST /red_flags evaluates whether the symptom set already contains a clinical red flag that warrants immediate emergency triage — for example, chest pain with shortness of breath. This shortcut lets a triage app escalate to 'go to emergency department' without making the user answer 20 questions first.

POST /red_flags with evidence containing chest pain and shortness of breath; if any red flag is returned, route the user to emergency triage immediately.

AI Healthcare Agent

An LLM agent acting as a virtual medical assistant uses Infermedica as its grounded clinical reasoning tool. Through Jentic, the agent searches by intent (e.g., 'run a symptom check'), loads the schema, and calls /parse, /diagnosis, /red_flags, and /triage in sequence. This keeps clinical reasoning anchored to a regulated medical knowledge base rather than hallucinated by the LLM.

Parse a free-text complaint with /parse, run /diagnosis to convergence, then call /triage on the final evidence set and return the recommended care level.

Key Endpoints

16 endpoints — infermedica is an ai-powered clinical decision support api for symptom checking, differential diagnosis, and patient triage.

METHOD

PATH

DESCRIPTION

POST

/diagnosis

Run a step of the adaptive diagnostic interview

POST

/triage

Get a triage level for the current evidence

POST

/parse

Parse free-text symptoms into concept IDs

POST

/red_flags

Detect emergency red flags in the evidence set

POST

/suggest

Suggest related symptoms to ask about

GET

/symptoms

List all symptoms in the catalogue

GET

/conditions

List all conditions in the catalogue

GET

/search

Free-text search across the medical concept graph

POST

/diagnosis

Run a step of the adaptive diagnostic interview

POST

/triage

Get a triage level for the current evidence

POST

/parse

Parse free-text symptoms into concept IDs

POST

/red_flags

Detect emergency red flags in the evidence set

POST

/suggest

Suggest related symptoms to ask about

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Infermedica's paired App-Id and App-Key are stored encrypted in the Jentic vault (MAXsystem). Agents call Infermedica operations through scoped Jentic credentials and never see either raw value, which matters for medical APIs subject to partnership-level audit requirements.

Intent-based discovery

Agents search Jentic with intents like 'run a symptom check' or 'get a triage level' and Jentic returns the matching Infermedica operations with their input schemas. The agent learns the /diagnosis evidence shape from the schema rather than reading the medical-domain docs.

Time to first call

Direct Infermedica integration: 1-3 days for the dual-header auth, evidence-list contracts, and looped /diagnosis state handling. Through Jentic: under an hour — schema-first execution removes most of the contract reading.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Stripe API

Stripe processes payments and subscriptions for telehealth services that Infermedica triages.

Use Stripe alongside Infermedica when the symptom checker leads into a paid consultation booking and you need to charge the patient or insurer.

Complementary

Twilio API

Twilio handles SMS and voice channels that telehealth and triage flows use to contact patients.

Use Twilio to deliver triage outcomes via SMS or to start a voice consultation when Infermedica's /triage returns 'consultation'.

FAQs

Specific to using Infermedica API API through Jentic.

What authentication does the Infermedica API use?

The Infermedica API uses paired App-Id and App-Key headers — both are required on every request. Through Jentic, both credentials are stored encrypted in the MAXsystem vault and injected at execution time so the agent never holds either raw value.

Can I parse free-text symptoms into Infermedica concept IDs?

Yes. POST /parse takes a free-text narrative (e.g., 'severe headache and nausea since yesterday') and returns Infermedica concept IDs and the surface text that mentioned them, ready to drop into the evidence list for /diagnosis or /triage.

What are the rate limits for the Infermedica API?

Rate limits depend on the partnership tier — sandbox accounts have low limits, and production limits are negotiated with Infermedica during integration. Check developer.infermedica.com or your partnership agreement for exact ceilings.

How do I run a symptom check through Jentic?

Search Jentic for 'run a symptom check' to find POST /diagnosis. Load the schema (sex, age, evidence array), execute, and call /diagnosis again with each new answer until 'should_stop' is true. Then call POST /triage on the same evidence. Get started at https://app.jentic.com/sign-up.

Does the API include emergency red flag detection?

Yes. POST /red_flags evaluates an evidence set against Infermedica's red-flag rules and returns the matching flags so a triage application can escalate to emergency care without completing a full interview. Use this as a safety pre-check on any symptom-check flow.

Is Infermedica suitable for clinical or only consumer applications?

Infermedica is used in both. The same v3 API powers patient-facing symptom checkers and call-centre triage tools. Regulatory clearance and intended-use disclaimers depend on the deployment market — Infermedica's compliance team works with partners on CE marking and FDA pathways.