Install Jentic One Beta

Connect the mdhub API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the mdhub 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%2Fmdhub.ai%2Fmdhub" | 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%2Fmdhub.ai%2Fmdhub" | 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 mdhub API.

Submit a standardized PHQ-9, GAD-7, or MADRS questionnaire as raw integer scores with mdhubType, and get an AI summary and numeric score generated automatically

Search open Slot resources by schedule, status, and start, then book an Appointment or reschedule it with an update

Submit a CoverageEligibilityRequest to verify behavioral health benefits such as session limits and TMS or IOP authorization, then read the CoverageEligibilityResponse

Retrieve the transcript for a session by sessionId and page through AI-coordinator calls with pageSize and pageToken

GET STARTED

Start building with mdhub API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use mdhub API for, with concrete tasks.

★ Agent-assisted clinic operations through Jentic

A clinic operations agent can handle scheduling and intake through Jentic: it searches open Slot resources for a provider's schedule, books the Appointment, and after the visit submits the patient's PHQ-9 scores so mdhub produces its AI summary and score. Each FHIR call carries a scope such as system/Appointment.write, so the agent's reach matches the work it does.

Search Slot with schedule set to the provider's schedule id and status free, book an Appointment in the first slot for patient 123, then submit an mdhub-phq-9 questionnaire with nine integer responses for that patient

Measurement-based care tracking

Behavioral health practices track symptom scores over time. The submit-mdhub route accepts only the integer scores for PHQ-9 (9 items, 0 to 3), GAD-7 (7 items, 0 to 3), or MADRS (10 items, 0 to 6), validates them against the stored questionnaire, and returns detailed issues on a bad length or range. Results are also readable as FHIR Observation resources for trend reporting.

Submit an mdhub-gad-7 questionnaire for patientId p_456 with responses [1,2,0,1,3,2,1], then search Observation for that patient to confirm the new score is recorded

Benefits verification before TMS or IOP

Interventional treatments such as TMS and intensive outpatient programs need authorization. Creating a CoverageEligibilityRequest asks mdhub to verify behavioral health benefits, including session limits, cost-share detail, and authorization status, and the resulting CoverageEligibilityResponse can be searched by patient or request.

Read the patient's Coverage, submit a CoverageEligibilityRequest for that patient and insurer, then search CoverageEligibilityResponse by request and report the session limits returned

Key Endpoints

86 endpoints — the mdhub api reads from and writes to the mdhub behavioral health clinical record through two surfaces: a proprietary v1 api for patients, session transcripts, ai-coordinator calls, and questionnaires, and a standards-based hl7 fhir r4 api for the same underlying data.

METHOD

PATH

DESCRIPTION

POST

/questionnaires/submit-mdhub

Submit a standardized PHQ-9, GAD-7, or MADRS questionnaire

POST

/sessions/getTranscript

Get a session transcript

GET

/calls/all

List AI-coordinator calls

GET

/Patient

Search FHIR patients

GET

/Slot

Search bookable slots

POST

/Appointment

Book an appointment

POST

/CoverageEligibilityRequest

Submit an eligibility request

POST

/Subscription

POST

/questionnaires/submit-mdhub

Submit a standardized PHQ-9, GAD-7, or MADRS questionnaire

POST

/sessions/getTranscript

Get a session transcript

GET

/calls/all

List AI-coordinator calls

GET

/Patient

Search FHIR patients

GET

/Slot

Search bookable slots

POST

/Appointment

Book an appointment

POST

/CoverageEligibilityRequest

Submit an eligibility request

POST

/Subscription

Why Jentic?

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

Setup

Wiring mdhub by hand means juggling two credentials: an x-api-key for the v1 routes and a short-lived OAuth client_credentials token for FHIR R4 that must carry the right SMART scopes. Through Jentic you install once, import mdhub from the API Directory, store both credentials once, and your agent calls it.

Permission scoping

mdhub's FHIR routes put the resource type in the URL path (/Patient, /Appointment, /DocumentReference) and the record id on reads and updates (/Patient/{id}), so a rule can bound your agent to the resource types and operations you pick. You choose the operations it may call, so sensitive ones like reading session transcripts or updating medication requests are not included unless you add them.

Credential isolation

Your mdhub API key and OAuth client secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'book a patient appointment' or 'submit a PHQ-9 score', and Jentic returns the matching mdhub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using mdhub API through Jentic.

What authentication does the mdhub API use?

Per its OpenAPI spec, the mdhub API uses two schemes. The proprietary v1 routes, such as patients, session transcripts, calls, and questionnaire submission, take an API key in the x-api-key header. The FHIR R4 routes use OAuth 2.0 client credentials under the SMART Backend Services profile, with SMART v2 system scopes such as system/Patient.read, and access tokens last 5 minutes. Through Jentic both credentials are stored encrypted on your own instance and injected at call time.

Is there an mdhub MCP server?

You don't need an MCP server to give your agent mdhub. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so the agent's context is not loaded with another server's tool definitions.

Can I limit what my agent is allowed to do with the mdhub API?

Yes. For a scheduling agent, write a rule that allows only GET /Slot, GET /Schedule, and POST /Appointment, so it can find open slots and book visits but cannot read clinical documents, medications, or session transcripts. You can also register the OAuth client with only the scopes it needs, such as system/Appointment.write. Every call the agent makes is logged.

What are the rate limits for the mdhub API?

The spec states default limits of 100 requests per minute and 1000 requests per hour per API key, with higher custom limits on enterprise plans. The FHIR API is limited per client credential at the same default tier. Exceeding a limit returns Too Many Requests.

Can I submit PHQ-9 or GAD-7 scores with the mdhub API?

Yes. POST /questionnaires/submit-mdhub takes a patientId, an mdhubType such as mdhub-phq-9, mdhub-gad-7, or mdhub-madrs, and a responses array of integer scores. mdhub validates the length and range against the stored questionnaire, maps each score to its label, and generates an AI summary and numeric score. Custom intake forms go through POST /questionnaires/submit instead.

How do I book an appointment in mdhub through Jentic?

Search Jentic for an intent like 'book a patient appointment in mdhub', import the mdhub API, and store your OAuth client credentials once. Your agent then calls GET /Slot to find a free slot and POST /Appointment with the slot and participants. To run it on your own infrastructure, install Jentic One from its GitHub repo.

mdhub API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareEhr EmrapiKey, oauth286 EndpointsREST

For Agents

Create and update patients, book appointments from open slots, submit PHQ-9, GAD-7, and MADRS scores, check behavioral health insurance eligibility, and pull session transcripts and AI-coordinator call logs from an mdhub clinic.

Use for: Submit a PHQ-9 score for this patient, Find open appointment slots with Dr. Patel next week, Book an intake appointment for a new patient, Check whether this patient's insurance covers TMS sessions

Not supported: Does not handle claims submission, payment collection, e-prescribing to pharmacies, or video visits. Use for reading and writing mdhub behavioral health records, scheduling, and questionnaires only.

The mdhub API reads from and writes to the mdhub behavioral health clinical record through two surfaces: a proprietary v1 API for patients, session transcripts, AI-coordinator calls, and questionnaires, and a standards-based HL7 FHIR R4 API for the same underlying data. The FHIR side covers Patient, Coverage, eligibility checks with TMS and IOP authorization status, Condition, medications, allergies, Consent, providers, locations, Schedule, Slot, Appointment, Encounter, Observation, questionnaires, DocumentReference, ServiceRequest, and Subscription webhooks. Standardized PHQ-9, GAD-7, and MADRS questionnaires can be submitted as raw integer scores, after which mdhub generates an AI summary and a numeric score.

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

75%

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

29%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

51%

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

44%

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.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

88%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B+Signals: 1

68%

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: B+Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the mdhub API to your agent

Capabilities

Start building with mdhub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

mdhub API

Jentic AI Readiness Score

mdhub 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