canonical: https://jentic.com/apis/tavus.io/tavus

# Tavus API

Tavus API enables creation and management of AI video replicas, personas, and real-time conversations powered by digital twins. The API exposes 36 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a persona, list personas. Covers 36 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Create a persona
- List personas
- Get a persona
- Update a persona
- Delete a persona

## Use cases

### Communications Operations

Use the Tavus API to perform communications operations programmatically. The API provides 36 endpoints covering core functionality including create a persona, list personas, get a persona.

Example prompt: Call POST `/v2/personas` to create a persona

### Automated Conversations Management

Automate conversations operations by combining multiple Tavus API endpoints. Agents can list personas and then get a persona in a single workflow.

Example prompt: Call GET `/v2/personas` to list personas, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tavus API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create a persona', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/personas` | Create a persona |
| GET | `/v2/personas` | List personas |
| GET | `/v2/personas/{persona_id}` | Get a persona |
| PATCH | `/v2/personas/{persona_id}` | Update a persona |
| DELETE | `/v2/personas/{persona_id}` | Delete a persona |
| POST | `/v2/replicas` | Create a replica |
| GET | `/v2/replicas` | List replicas |
| GET | `/v2/replicas/{replica_id}` | Get a replica |

## Key resources

- **Conversations** — Operations for conversations
- **Documents** — Operations for documents
- **Guardrails** — Operations for guardrails
- **Objectives** — Operations for objectives
- **Personas** — Operations for personas

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 59 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/tavus.io/tavus/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 the Tavus API by hand means sending its x-api-key header on every request, targeting the tavusapi.com host, and building your own retry handling across its persona and replica endpoints. Through Jentic you install once, import the Tavus API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Tavus API puts the persona and replica ids in the URL path (`/v2/personas/{persona_id}`, `/v2/replicas/{replica_id}`), so a rule can pin your agent to one persona or replica: it can read and list them. You choose the operations it may call, so destructive ones like deleting a persona or patching one are not included unless you add them.
- **Credential handling:** Your Tavus API key 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 'create a persona' or 'get a replica', and Jentic returns the matching Tavus API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Tavus API use?

The Tavus API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a persona with the Tavus API?

Yes. Use the POST `/v2/personas` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tavus API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a persona through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a persona'. Jentic returns the matching Tavus API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tavus API have?

The Tavus API exposes 36 endpoints covering conversations, documents, guardrails operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tavus API operations and credentials the agent may use. Since the Tavus API carries the persona and replica ids in the URL path (`/v2/personas/{persona_id}` and `/v2/replicas/{replica_id}`), you can pin the agent to a single persona or replica and allow only read and list calls. Destructive operations like deleting a persona (DELETE `/v2/personas/{persona_id}`) or patching one are excluded unless you explicitly grant them.