Elai API

Name: Elai API
Brand: Elai API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processingbearer20 EndpointsREST

For Agents

Generate, render, translate, and personalise AI avatar videos from text or presentations, and stream them in real time.

Install Jentic One Beta

Connect the Elai API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Elai 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Elai API.

Create new AI avatar videos from text, presentations, or templates

Render and re-render videos and produce personalised batches against a template

Translate an existing video into another language while preserving the avatar performance

GET STARTED

Start building with Elai API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Elai API for, with concrete tasks.

★ Personalised sales-outreach videos at scale

A sales team wants to send each prospect a short video addressing them by name and referencing their company. The Elai API supports a personalised-batch render against a template, so a single template plus a CSV of prospects produces hundreds of unique videos. A webhook fires per render so the outreach tool knows when a given video is ready to send.

POST /videos/renderTemplate/{videoId} with the prospect list, then handle the webhook delivered to the subscribed endpoint to email each finished video to the right prospect.

Multilingual training video production

A learning team produces a base course in English and needs Spanish, French, and Portuguese versions. The Elai translate-video endpoint takes an existing videoId and a target language, returning a new translated video without re-shooting. Combined with the avatars and voices listings, the team can pick a localised voice per language for a consistent feel.

Call POST /videos/translate/{videoId} for each target language, then poll GET /videos/{videoId} or wait for the webhook before publishing the translated versions.

Slide-deck-to-video automation

A content team uploads a presentation and wants Elai to generate a complete video from it. POST /videos/from-presentation accepts the deck, POST /story/generate-slides/{videoId} expands the storyline, and POST /gpt/{videoId} polishes the script before rendering. The result is a turnkey deck-to-video pipeline that runs without manual scene editing for routine content.

POST /videos/from-presentation with the deck, then POST /story/generate-slides/{videoId} and POST /videos/render/{videoId} once the script is approved.

Real-time avatar stream for a live event

An interactive product demo or live event drives a real-time AI avatar to respond to operator prompts. POST /streams opens a session, PUT /streams/{streamId} starts it, and DELETE /streams/{streamId} closes it cleanly. The streams resource decouples real-time use cases from the asynchronous render pipeline.

POST /streams to allocate the stream, PUT /streams/{streamId} when the operator goes live, and DELETE /streams/{streamId} after the event ends.

Elai as an agent video tool through Jentic

An AI agent platform exposes 'make a short video' as a callable tool. Through Jentic, the agent searches by intent, receives the right Elai operation, and runs the render with the bearer token Jentic injects at execution time. The agent does not need to handle Elai's auth or pick between 20 endpoints by hand.

Search Jentic for 'create an AI avatar video from a script', load POST /videos plus POST /videos/render/{videoId}, and run them in sequence to deliver a finished video URL.

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for elai api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/videos

Create a video

POST

/videos/render/{videoId}

Render a video

POST

/videos/translate/{videoId}

Translate a video

POST

/videos/renderTemplate/{videoId}

Render personalised batch from template

POST

/videos/from-presentation

Create a video from a presentation

POST

/streams

Create a real-time avatar stream

GET

/avatars

List avatars

POST

/webhooks/subscribe

Subscribe to a webhook

POST

/videos

Create a video

POST

/videos/render/{videoId}

Render a video

POST

/videos/translate/{videoId}

Translate a video

POST

/videos/renderTemplate/{videoId}

Render personalised batch from template

POST

/videos/from-presentation

Create a video from a presentation

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Elai bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Jentic injects the Authorization header at execution time, so agents only ever receive scoped execution access — the raw token never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent — 'create an AI avatar video', 'translate a video', 'render a personalised batch' — and Jentic returns the matching Elai operation along with its input schema, mapping intent to the right entry in the 20-endpoint surface.

Time to first call

Direct integration: 2-3 days for auth, render polling, and webhook handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Elai API through Jentic.

Why is there no official OpenAPI spec for Elai API?

Elai does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Elai API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Elai API use?

Elai uses HTTP bearer authentication. Pass your API key in the Authorization: Bearer header on every request. Jentic stores the key encrypted in its vault and injects it at execution time so the agent never sees the raw secret.

Can I translate an existing video into another language?

Yes. POST /videos/translate/{videoId} takes an existing video and a target language and returns a new translated video, preserving the avatar performance.

How do I render a personalised batch from a template?

Configure a template video in Elai, then call POST /videos/renderTemplate/{videoId} with the per-recipient variables. Each recipient gets a unique render and the webhook fires when each one finishes.

What are the rate limits for the Elai API?

Rate limits are not declared in the OpenAPI spec and depend on your Elai subscription tier. Render-heavy workloads should subscribe to the webhook via POST /webhooks/subscribe rather than polling GET /videos/{videoId}.

How do I create a video through Jentic?

Install the SDK with pip install jentic, search Jentic for 'create an AI avatar video', load the POST /videos schema, and execute with your script and avatar choice. Jentic injects the bearer token and returns the video ID for follow-up render and download calls.

Elai API

Connect the Elai API to your agent

Capabilities

Start building with Elai API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs