Install Jentic One Beta

Connect the DodoDentist API to your agent

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

Schedule, reschedule, retrieve, and cancel dental appointments

Create, retrieve, update, and remove patient records

List clinics and the treatments they offer

List invoices and payments for the practice

Create, update, and delete webhook subscriptions for practice events

GET STARTED

Start building with DodoDentist API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DodoDentist API for, with concrete tasks.

★ Agent Appointment Booking

An AI agent connected through Jentic looks up a patient, books their dental appointment, and reschedules or cancels it when plans change. The DodoDentist API exposes the full appointment lifecycle plus patient records, and Jentic injects the credential at call time so the agent never holds the key.

Create a patient if needed, book a dental appointment for them, and reschedule it to a later slot

Patient Records Management

Practices keep patient records current as people register and update their details. The DodoDentist API creates, retrieves, updates, and removes patient records, so an agent can maintain an accurate roster tied to appointments and billing.

Create a new patient record and update it with corrected contact details

Practice Event Webhooks

Integrations react to new and changed appointments as they happen. The DodoDentist API creates, updates, and deletes webhook subscriptions, so an agent can keep reminder and reporting systems notified of practice events.

Create a webhook subscription for appointment events and confirm it was registered

Key Endpoints

18 endpoints — the dododentist api runs the front-desk operations of a dental practice.

METHOD

PATH

DESCRIPTION

GET

/api/appointments

List appointments

POST

/api/appointments

Create an appointment

PUT

/api/appointments/{appointmentId}

Update an appointment

DELETE

/api/appointments/{appointmentId}

Cancel an appointment

GET

/api/patients

List patients

POST

/api/patients

Create a patient

GET

/api/treatments

List treatments

POST

/api/webhooksubscriptions

Create a webhook subscription

GET

/api/appointments

List appointments

POST

/api/appointments

Create an appointment

PUT

/api/appointments/{appointmentId}

Update an appointment

DELETE

/api/appointments/{appointmentId}

Cancel an appointment

GET

/api/patients

List patients

POST

/api/patients

Create a patient

GET

/api/treatments

List treatments

POST

/api/webhooksubscriptions

Create a webhook subscription

Why Jentic?

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

Setup

Wiring DodoDentist by hand means base64-encoding your API key secret for HTTP Basic auth and switching to the `Authorization`-header apiKey for webhook operations yourself. Through Jentic you install once, import DodoDentist from the API Directory, store the credential once, and your agent calls it.

Permission scoping

DodoDentist puts resource ids like the appointment id and patient id in the URL path, so a rule can bound the agent to read paths and specific operations. Limit the agent to the operations it needs, such as listing and creating appointments, so destructive operations like deleting a patient or an appointment are not included unless you add them.

Credential isolation

Your DodoDentist 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 'book an appointment' or 'create a patient', and Jentic returns the matching DodoDentist operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using DodoDentist API through Jentic.

What authentication does the DodoDentist API use?

The DodoDentist 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. 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 schedule dental appointments with the DodoDentist API?

Yes. The API schedules, reschedules, retrieves, and cancels appointments, and manages patient records end to end. It also lists clinics and treatments, reports invoices and payments, and can notify your systems of practice events through webhook subscriptions.

Is there a DodoDentist MCP server?

You don't need an MCP server to give your agent the DodoDentist API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the appointment and patient 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 DodoDentist API?

Yes. Write a rule that allows only the appointment read and create operations, so the agent can book and look up appointments but cannot delete patients, appointments, or webhook subscriptions. Every call the agent makes is logged.

What are the rate limits for the DodoDentist API?

The OpenAPI spec does not specify rate limits. Check the DodoDentist documentation at https://dododentist.com for current limits before running high-volume scheduling or record jobs.

How do I book an appointment with the DodoDentist API through Jentic?

Search Jentic for an intent like 'create an appointment', add the DodoDentist API from the directory, and store your credential once. Your agent then looks up or creates the patient and books the appointment. To run it on your own infrastructure, install Jentic One from its GitHub repo.

DodoDentist API

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareAppointment Schedulingbasic, apiKey18 EndpointsREST

For Agents

Schedule and manage dental appointments, maintain patient records, list clinics, treatments, invoices, and payments, and subscribe to practice webhooks with DodoDentist.

Use for: Book a dental appointment for a patient, Reschedule an existing appointment, Cancel an appointment, Create a new patient record

Not supported: Does not handle clinical charting, insurance claim adjudication, or lab orders. Use for dental appointment scheduling, patient records, and practice billing only.

The DodoDentist API runs the front-desk operations of a dental practice. It schedules, reschedules, retrieves, and cancels appointments, and manages patient records end to end. It lists clinics and the treatments they offer, reports invoices and payments, and manages webhook subscriptions that notify your systems of practice events.

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

25%

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.

69%

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: DSignals: 4

14%

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.

64%

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

30%

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

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DodoDentist API to your agent

Capabilities

Start building with DodoDentist API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DodoDentist API

Jentic AI Readiness Score

DodoDentist 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