Official vendor OpenAPI document · agent-readyPaymentsBilling Subscriptionsbearer11 EndpointsREST
For Agents
Enroll a company in a Denta dental membership by stepping through its ordered signup sequence. Submit company details, start checkout, elect coverage, authorize card funding, and read or restart the application.
Use for: Read the Denta signup sequence, Submit company and seat details to start enrollment, Start the membership at checkout, Set the company address for the application
Not supported: Does not handle dental claims, appointment booking, or clinical records. Use for enrolling a company in a Denta membership only.
The Denta API runs a fixed, ordered enrollment sequence that signs a company up for a Denta dental membership. After a device-flow authorization mints a bearer token, an agent works through five steps in order: company and seats, checkout, company address, coverage election, and authorizing card funding. The API refuses out-of-order requests and names the current step, and the full application record can be read or restarted at any point.
Install Jentic One Beta
Connect the Denta to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Denta, 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.
1
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%2Fdenta.com%2Fdenta" | sh2
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%2Fdenta.com%2Fdenta" | 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.
Capabilities
What an agent can do with Denta API.
Read the ordered signup sequence and where the application currently stands
Submit company and seat details to begin enrollment
Start the Denta membership at checkout
Set the company address and elect plan coverage
Authorize card funding by signing the funding request
Read the complete application record on file or restart it from step one
Use Cases
Patterns agents use Denta API for, with concrete tasks.
★ Guided Membership Enrollment
An AI agent enrolls a company in a Denta membership by following the sequence the API enforces: it reads the current step, submits company and seat details, starts checkout, sets the address, elects coverage, and authorizes card funding. The agent discovers each step operation through Jentic by intent, and because the API refuses out-of-order calls, the agent follows the order the start operation returns.
Read the signup sequence, then submit company details, start checkout, set the address, elect coverage, and authorize card funding in order
Resume or Restart an Application
A partially completed enrollment needs to be resumed or cleared. The agent reads the sequence to learn which step the application is on, continues from there, or restarts to clear the application and return to step one. Denta tracks the step server-side, so the agent always knows where to pick up.
Read the current step for an application, then either continue the next step or restart it from step one
Audit the Application Record
Before authorizing funding, a reviewer agent reads the complete application record on file and the document that the signing step is about to act on. This lets the agent confirm the company, seats, address, and coverage are correct before any money-moving step runs. The record and document reads do not change state.
Read the full application record and the document the signing step will act on, and return a summary for review
Key Endpoints
11 endpoints — the denta api runs a fixed, ordered enrollment sequence that signs a company up for a denta dental membership.
METHOD
PATH
DESCRIPTION
GET
/api/v1/start
Get the signup sequence and current step
POST
/api/v1/signup
Step 1: company and seats
POST
/api/v1/checkout
Step 2: start the membership
PATCH
/api/v1/company/address
Step 3: company address
PUT
/api/v1/plan/coverage
Step 4: coverage election
POST
/api/v1/documents/sign-request
Step 5: authorize card funding
GET
/api/v1/application
Read the complete application record
POST
/api/v1/restart
Clear the application and return to step one
GET
/api/v1/start
Get the signup sequence and current step
POST
/api/v1/signup
Step 1: company and seats
POST
/api/v1/checkout
Step 2: start the membership
PATCH
/api/v1/company/address
Step 3: company address
PUT
/api/v1/plan/coverage
Step 4: coverage election
POST
/api/v1/documents/sign-request
Step 5: authorize card funding
GET
/api/v1/application
Read the complete application record
POST
/api/v1/restart
Clear the application and return to step one
Jentic AI Readiness Score
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.
D
Denta
- Foundational (C+)59/100
100
Foundational Compliance59
Developer Experience & Jentic Compatibility36
AI-Readiness & Agent Experience94
Agent Usability60
Security69
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
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.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
36%
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.
36
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
55%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
69
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
69%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Denta by hand means running its device-flow authorization to mint a bearer token and then calling the five signup steps in the exact order the API enforces, since an out-of-order request is refused. Through Jentic you install once, import Denta from the API Directory, store the token once, and your agent calls it.
Permission scoping
You choose which Denta operations your agent may call, so reads like the sequence and the application record can run while checkout and the card-funding signature stay out unless you add them. That keeps the money-moving steps off the table until you allow them.
Credential isolation
Your Denta 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 read the signup sequence or start checkout, and Jentic returns the matching Denta operation with its input schema so the agent calls the right step without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Denta API through Jentic.
What authentication does the Denta API use?
The Denta API authenticates with a bearer token minted by its device-flow authorization and sent in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs.
Can I complete a membership signup with the Denta API?
Yes. The API exposes a five-step sequence: submit company and seats, start checkout, set the company address, elect coverage, and authorize card funding. Requests sent out of order are refused with the step the application is currently on, so follow the order the start operation returns.
What are the rate limits for the Denta API?
The OpenAPI spec does not publish rate limits for the Denta API. Check Denta's own documentation for current limits before polling the device-token step while waiting for a human to approve.
Can I limit what my agent is allowed to do with the Denta API?
Yes. Write a rule that allows only the read operations such as the sequence and the application record, so the agent can inspect progress while checkout and the card-funding signature stay out unless you add them. Every call the agent makes is logged.
How do I run the signup with the Denta API through Jentic?
Complete the device-flow authorization, search Jentic for an intent like read the signup sequence, store your token once, and your agent calls each step operation in the order the API enforces. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Denta MCP server?
You don't need an MCP server to give your agent the Denta API. Jentic connects it directly from the API Directory: import it, authorize once, store your token, and your agent calls the step operations it needs on demand.
GET STARTED