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

# Tavusapi Tavus Developer API Collection

We're an AI video research company making personalized video possible at scale. Generate videos of yourself, and never record again! Available via web app & developer APIs. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create replica, list replicas. Covers 8 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create Replica
- List Replicas
- Get Replica
- Delete Replica
- Rename Replica
- Generate Video

## Use cases

### Education Operations

Use the Tavus Developer API Collection to perform education operations programmatically. The API provides 8 endpoints covering core functionality including create replica, list replicas, get replica.

Example prompt: Call POST `/v2/replicas` to create replica

### Automated Replicas Management

Automate replicas operations by combining multiple Tavus Developer API Collection endpoints. Agents can list replicas and then get replica in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Tavus Developer API Collection 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 replica', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/replicas` | Create Replica |
| GET | `/v2/replicas` | List Replicas |
| GET | `/v2/replicas/{replica_id}` | Get Replica |
| DELETE | `/v2/replicas/{replica_id}` | Delete Replica |
| PATCH | `/v2/replicas/{replica_id}/name` | Rename Replica |
| POST | `/v2/videos` | Generate Video |
| DELETE | `/v2/videos/{video_id}` | Delete Video |
| PATCH | `/v2/videos/{video_id}/name` | Rename Video |

## Key resources

- **Replicas** — Operations related to Replicas
- **Videos** — Operations related to Videos

## Why Jentic

- **Setup:** Wiring the Tavus Developer API Collection 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 replica and video endpoints. Through Jentic you install once, import the Tavus Developer API Collection from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Tavus Developer API Collection puts the replica and video ids in the URL path (`/v2/replicas/{replica_id}`, `/v2/videos/{video_id}`), so a rule can pin your agent to one replica or video: it can read and rename them. You choose the operations it may call, so destructive ones like deleting a replica or a video 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 replica' or 'generate a video', and Jentic returns the matching Tavus Developer API Collection operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Schoology** — Alternative education API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the Tavus Developer API Collection use?

The Tavus Developer API Collection 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 replica with the Tavus Developer API Collection?

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

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

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 replica through Jentic?

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

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

The Tavus Developer API Collection exposes 8 endpoints covering replicas, videos operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and you pick the exact endpoints it can call. Since the Tavus API puts replica and video ids in the URL path (`/v2/replicas/{replica_id}`, `/v2/videos/{video_id}`), you can pin the agent to a single replica or video and grant only read and rename access. Destructive operations such as deleting a replica or a video stay out of reach unless you explicitly add them.