For Agents
Manage a medical practice with Doctofam: list and create patients and appointments, retrieve clinics and procedures, record invoices and payments, and subscribe to practice webhooks.
Use for: List all patients in the practice, Create a new patient record, Book an appointment for a patient, Get an invoice by its id
Not supported: Does not handle clinical lab results, e-prescribing, or insurance claim adjudication. Use for managing patient records, appointments, and billing in a medical practice only.
The Doctofam API manages the records of a medical practice: patients, appointments, clinics, procedures, invoices, and payments. It lists, creates, and retrieves patient records and appointments, records invoices and payments, and reports the clinics and procedures available. Webhook-subscription operations push practice events to your own systems.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Doctofam 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%2Fdoctofam.com%2Fdoctofam" | shStep 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%2Fdoctofam.com%2Fdoctofam" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Doctofam API.
List, create, and retrieve patient records
Book and retrieve appointments for a patient
Create and retrieve invoices and record payments
List clinics and the procedures they offer
Create, update, and delete webhook subscriptions for practice events
Patterns agents use Doctofam API for, with concrete tasks.
★ Agent Practice Assistant
An AI agent connected through Jentic looks up a patient, books their appointment, and raises the matching invoice. The Doctofam API exposes the patient, appointment, and invoice operations the agent needs, and Jentic injects the credential at call time so the agent never holds the key.
Look up a patient by listing patients, create an appointment for them, and create the corresponding invoice
Billing and Payments
Front-desk workflows raise invoices and record payments as they come in. The Doctofam API creates and retrieves invoices and payments, so an agent can reconcile a patient's balance against the services recorded.
Create an invoice for a completed procedure and record the patient's payment against it
Practice Event Webhooks
Integrations react to new appointments and patients as they happen. The Doctofam API creates, updates, and deletes webhook subscriptions, so an agent can keep downstream systems notified of practice events.
Create a webhook subscription for appointment events and confirm it was registered
21 endpoints — the doctofam api manages the records of a medical practice: patients, appointments, clinics, procedures, invoices, and payments.
METHOD
PATH
DESCRIPTION
/api/patients
List patients
/api/patients
Create a patient
/api/appointments
List appointments
/api/appointments
Create an appointment
/api/invoices
List invoices
/api/invoices
Create an invoice
/api/payments
Create a payment
/api/webhooksubscriptions
Create a webhook subscription
/api/patients
List patients
/api/patients
Create a patient
/api/appointments
List appointments
/api/appointments
Create an appointment
/api/invoices
List invoices
/api/invoices
Create an invoice
/api/payments
Create a payment
/api/webhooksubscriptions
Create a webhook subscription
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Doctofam by hand means base64-encoding your API key secret for HTTP Basic auth, switching to the `Authorization`-header apiKey for webhook operations, and tracking per-resource scopes yourself. Through Jentic you install once, import Doctofam from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Doctofam puts resource ids like the patient id in the URL path, so a rule can bound your agent to specific read paths and operations. Limit the agent to the operations it needs, such as listing and reading patients and appointments, so write operations like creating invoices or deleting webhook subscriptions are not included unless you add them.
Credential isolation
Your Doctofam credential 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 'list patients' or 'create an appointment', and Jentic returns the matching Doctofam operation with its input schema so the agent calls the right endpoint directly.
Alternatives and complements available in the Jentic catalogue.
Specific to using Doctofam API through Jentic.
What authentication does the Doctofam API use?
The Doctofam API authenticates with HTTP Basic auth, sending your base64-encoded API key secret, per its OpenAPI spec. Webhook-subscription operations instead use an apiKey credential in the `Authorization` header. Each key carries per-resource scopes, such as read access to patients or write access to appointments. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.
Can I manage patients and appointments with the Doctofam API?
Yes. The API lists, creates, and retrieves patient records and appointments, reports the clinics and procedures available, and records invoices and payments. Webhook subscriptions can notify your systems when practice events occur.
Is there a Doctofam MCP server?
You don't need an MCP server to give your agent the Doctofam API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the patient, appointment, and billing operations. Operations load on demand, so your agent's context stays lean instead of holding another server's tool definitions.
Can I limit what my agent is allowed to do with the Doctofam API?
Yes. Write a rule that allows only the read operations for patients, appointments, and invoices, so the agent can look up practice data but cannot create patients, record payments, or change webhook subscriptions. Every call the agent makes is logged.
What are the rate limits for the Doctofam API?
The OpenAPI spec does not specify rate limits. Check the Doctofam documentation at https://doctofam.com for current limits before running high-volume record or billing jobs.
How do I book an appointment with the Doctofam API through Jentic?
Search Jentic for an intent like 'create an appointment', add the Doctofam API from the directory, and store your credential once. Your agent then looks up the patient and creates the appointment and any invoice. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED