Install Jentic One Beta

Connect the MD-X Portal - API Dokumentation für Krankenkassen to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MD-X Portal - API Dokumentation für Krankenkassen, 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%2Fqs-mdx.mdportal.de%2Fqs-mdx-mdportal" | 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%2Fqs-mdx.mdportal.de%2Fqs-mdx-mdportal" | 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 MD-X Portal - API Dokumentation für Krankenkassen API.

Search Vorgänge by typisierung and a status such as SENT, ANSWERED, or REJECTED, with offset and limit paging

Fetch cases ready for processing in a kontext such as EV_DOWNLOAD or EV_ABLEHNUNG and acknowledge each by processId

Upload an eVV document to an existing case with a documentTitle, and download one or several documents as a ZIP

Create an Erörterungsverfahren request with krankenhaus, auftrag, versicherter, and aufenthalt details, then edit or read it

GET STARTED

Start building with MD-X Portal - API Dokumentation für Krankenkassen API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MD-X Portal - API Dokumentation für Krankenkassen API for, with concrete tasks.

★ Agent-run case inbox through Jentic

A claims-operations agent at a health insurer works the MD-X inbox: it fetches cases ready for download, acknowledges each by processId, and downloads the documents for the case worker. Through Jentic the portal JWT is injected by the developer's own Jentic One instance, and rules keep the agent to read and acknowledge operations.

GET /v1/vorgang/todo with kontext 'EV_DOWNLOAD', then for each case POST /v1/vorgang/acknowledge with its processId and GET /v1/evv/dokumente/zip with the dokumentenIds

Erörterungsverfahren requests

When an insurer and hospital dispute a billing review, the insurer opens an Erörterungsverfahren. POST /v1/ev/anforderung requires krankenhaus, auftrag, versicherter, and aufenthalt, PATCH edits it by vorgang, and POST /v1/ev/stornierung cancels it with a stornierungsMeldung.

POST /v1/ev/anforderung with the krankenhaus, auftrag, versicherter, and aufenthalt objects for the stay, then POST /v1/vorgang/send with the returned processId

eVV document exchange

Cases carry documents under the eVV agreement. POST /v1/evv/dokument uploads a file to an existing case with a required documentTitle and optional beschreibung, GET /v1/evv/klassifikation returns the document classification, and GET /v1/evv/dokument downloads a single document by dokumentId.

POST /v1/evv/dokument with processId '4711', documentTitle 'Entlassbrief', and the PDF as dokument

Case status monitoring

GET /v1/vorgang/search filters cases by status, such as PROCESSING, ANSWERED, REJECTED, or FINISHED, so an agent can report which reviews moved and pull the latest Quittierung for each with GET /v1/quittierung.

GET /v1/vorgang/search with status 'ANSWERED' and limit 50, then GET /v1/quittierung for each processId

Key Endpoints

22 endpoints — the md-x portal api connects german statutory health insurers (krankenkassen) to the md-x portal of the medizinischer dienst, so their systems can exchange review cases (vorgänge) and the documents behind them.

METHOD

PATH

DESCRIPTION

GET

/v1/vorgang/todo

Cases ready for processing

GET

/v1/vorgang/search

Search cases

POST

/v1/vorgang/acknowledge

Acknowledge a case

POST

/v1/vorgang/send

Send a case

POST

/v1/evv/dokument

Upload an eVV document

GET

/v1/evv/dokumente/zip

Download several documents

POST

/v1/ev/anforderung

Create an Erörterungsverfahren

GET

/v1/vorgang/todo

Cases ready for processing

GET

/v1/vorgang/search

Search cases

POST

/v1/vorgang/acknowledge

Acknowledge a case

POST

/v1/vorgang/send

Send a case

POST

/v1/evv/dokument

Upload an eVV document

GET

/v1/evv/dokumente/zip

Download several documents

POST

/v1/ev/anforderung

Create an Erörterungsverfahren

Why Jentic?

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

Setup

Wiring the MD-X Portal by hand means obtaining a JWT bearer token, choosing between its two portal hosts, and threading processId through query parameters and multipart uploads yourself. Through Jentic you install once, import the MD-X Portal API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The MD-X Portal passes processId as a query parameter rather than a path segment, so rules bound which operations your agent may call, not which case. You choose the operations it may call, so destructive ones like case deletion or document deletion are not included unless you add them.

Credential isolation

Your MD-X Portal 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 'fetch cases ready for download' or 'upload an eVV document', and Jentic returns the matching MD-X Portal operation with its input schema so the agent calls the right endpoint without reading the German reference docs.

FAQs

Specific to using MD-X Portal - API Dokumentation für Krankenkassen API through Jentic.

What authentication does the MD-X Portal API use?

The MD-X Portal API declares an HTTP bearer scheme (bearerAuth) with a JWT format in its OpenAPI spec, applied globally. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Which servers does the MD-X Portal API use?

The spec lists two hosts: https://qs-mdx.mdportal.de/api/kk, whose qs- prefix marks it as the quality-assurance (test) host, and https://mdx.mdportal.de/api/kk. Point test integrations at the qs- host before switching to the other.

What are the rate limits for the MD-X Portal API?

The OpenAPI spec does not specify rate limits. List operations page with offset and limit, each capped at 100 in the spec. For current limits, ask the Medizinischer Dienst via the portal at https://mdx.mdportal.de.

How do I fetch cases ready for processing through Jentic?

Install Jentic One, import the MD-X Portal API from the Jentic API Directory, and store your portal token. Your agent searches for 'fetch MD-X cases ready for processing', Jentic returns GET /v1/vorgang/todo with its schema, and the agent calls it with a kontext such as EV_DOWNLOAD. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an MD-X Portal MCP server?

You don't need an MCP server to give your agent the MD-X Portal API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context.

Can I limit what my agent is allowed to do with the MD-X Portal API?

Yes. Write a rule that allows only GET /v1/vorgang/todo, POST /v1/vorgang/acknowledge, and GET /v1/evv/dokumente/zip, so the agent can work the download inbox while sending cases, deleting documents, or cancelling an Erörterungsverfahren stays out of reach. Every call it makes is logged.

Qs Mdx Mdportal De MD-X Portal - API Dokumentation für Krankenkassen

AI ReadinessFoundational (C-)51/100

See full scorecard

Community OpenAPI document · agent-readyHealthcareEhr Emrbearer22 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search and fetch MD-X Portal review cases for a German health insurer, acknowledge and send them, upload or download eVV documents, and create or cancel Erörterungsverfahren requests.

Use for: Find all MD-X cases with status ANSWERED, Get the cases waiting for download and acknowledge them, Upload the hospital discharge letter to case 4711, Download all documents for this case as a ZIP

Not supported: Does not access patient EHRs, submit hospital claims, or process payments. Use for exchanging review cases and eVV documents between German health insurers and the MD-X Portal only.

The MD-X Portal API connects German statutory health insurers (Krankenkassen) to the MD-X Portal of the Medizinischer Dienst, so their systems can exchange review cases (Vorgänge) and the documents behind them. It searches cases by status, fetches cases ready for processing, acknowledges and sends them, and uploads and downloads eVV documents, including several at once as a ZIP. It also creates, edits, reads, and cancels Erörterungsverfahren requests and returns receipts (Quittierung) and system notices.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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

100%

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

37%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

73%

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

52%

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.

42%

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 MD-X Portal - API Dokumentation für Krankenkassen to your agent

Capabilities

Start building with MD-X Portal - API Dokumentation für Krankenkassen API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Qs Mdx Mdportal De MD-X Portal - API Dokumentation für Krankenkassen

Jentic AI Readiness Score

MD-X Portal - API Dokumentation für Krankenkassen

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