Tavus API

Name: Tavus API
Brand: Tavus API
Availability: InStock

✓ Official Vendor SpecCommunicationsChat MessagingapiKey36 EndpointsREST

For Agents

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

Use for: I need to a persona, I want to personas, Search for a persona, Find all a persona

Install Jentic One Beta

Connect the Tavus API to your agent

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

Create a persona

List personas

Get a persona

Update a persona

GET STARTED

Start building with Tavus API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Tavus API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

36 endpoints — tavus api enables creation and management of ai video replicas, personas, and real-time conversations powered by digital twins.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Tavus API through Jentic.

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.

Tavus API

Connect the Tavus API to your agent

Capabilities

Start building with Tavus API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs