canonical: https://jentic.com/apis/denta.com/denta

# Denta

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.

## For AI 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.

## Scope

Does not handle dental claims, appointment booking, or clinical records. Use for enrolling a company in a Denta membership only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Read the full application record and the document the signing step will act on, and return a summary for review

## Key endpoints

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

## Key resources

- **Sequence** — Read the ordered signup sequence and the current step
- **Signup steps** — Submit company and seats, checkout, address, coverage election, and card-funding authorization
- **Application** — Read the complete application record or restart it
- **Authorization** — Begin the device-flow authorization and receive a bearer token

## AI readiness

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.

- **Score:** 59 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 36 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/denta.com/denta/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Stripe** — Stripe is a general subscription-billing platform; Denta runs a fixed dental-membership enrollment with coverage election built in.
- **Dentally** — Dentally manages dental practice operations and patients; Denta handles the membership enrollment and billing side.
- **Open Dental** — Open Dental is practice-management software for clinics; Denta covers the membership signup rather than clinical records.

## FAQ

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