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.

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" | 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%2Ftavusapi.com%2Ftavusapi" | 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 Developer API Collection API.

Create Replica

List Replicas

Get Replica

Delete Replica

Rename Replica

GET STARTED

Start building with Tavus Developer API Collection API

Explore with Jentic One

View OpenAPI Document

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.

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.

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.

Tavusapi Tavus Developer API Collection

AI ReadinessFoundational (D)47/100

See full scorecard

Community OpenAPI document · agent-readyEducationLmsapiKey8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

85%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

33%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

44%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tavus Developer API Collection to your agent

Capabilities

Start building with Tavus Developer API Collection API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tavusapi Tavus Developer API Collection

Jentic AI Readiness Score

Tavus Developer API Collection

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness