Tavusapi Tavus Developer API Collection
★ Only Publicly Available OpenAPI DocumentEducationLmsapiKey8 EndpointsREST
For Agents
Programmatically create replica, list replicas. Covers 8 operations with apiKey authentication.
Use for: I need to replica, I want to replicas, Search for replica, Find all replica
Not supported: Does not handle payments, communications, or crm - use for education only.
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.
Install Jentic One Beta
Connect the Tavus Developer API Collection to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tavus Developer API Collection, 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%2Ftavusapi.com%2Ftavusapi" | 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%2Ftavusapi.com%2Ftavusapi" | 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 Tavus Developer API Collection API.
Create Replica
List Replicas
Get Replica
Delete Replica
Rename Replica
Generate Video
Use Cases
Patterns agents use Tavus Developer API Collection API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'create replica', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
8 endpoints — we're an ai video research company making personalized video possible at scale.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 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 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
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe
Complementary API for broader integration workflows
Use alongside Tavus Developer API Collection for multi-service workflows
FAQs
Specific to using Tavus Developer API Collection API through Jentic.
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.
GET STARTED