Install Jentic One Beta

Connect the MakeAIVideo API to your agent

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

Get a free credit quote with POST /videos/estimate, then create a video from a tool brief or your own script with POST /videos and an idempotency_key

Poll render status with GET /videos/{id} respecting poll_after_seconds, or subscribe to video.ready and video.failed webhooks

Regenerate one scene with new narration, or redo the whole voiceover with a different voice_id

Download the finished MP4 through a signed URL and export captions as SRT or VTT

GET STARTED

Start building with MakeAIVideo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MakeAIVideo API for, with concrete tasks.

★ Agent-produced short videos through Jentic

A content agent follows the documented core loop: list tools, take a free estimate, create the video, poll until ready, and fetch the download URL. Through Jentic the agent discovers each operation by intent, the mav_ key stays in the developer's own Jentic One instance, and a rule can let the agent create and download videos while publishing and deletion stay out until you add them.

Call GET /tools, POST /videos/estimate with the chosen tool, POST /videos with tool, fields, and idempotency_key 'launch-teaser-1', poll GET /videos/{id}, then call GET /videos/{id}/download

Editing and regenerating parts of a video

When one scene misses the mark, POST /videos/{id}/scenes/{n}/regenerate redoes it with optional new narration instead of re-rendering everything. A different voice can be applied with POST /videos/{id}/voice and a required voice_id, and PATCH /videos/{id} edits the title, script, or caption settings before POST /videos/{id}/renders exports again.

POST /videos/vid_abc123/scenes/3/regenerate with narration 'Our new plan starts at ten dollars', then POST /videos/vid_abc123/renders to export again

Publishing to social platforms

Finished videos can go straight to the workspace's connected accounts. GET /publishing/accounts lists acc_ ids and whether each can post, POST /videos/{id}/publish takes account_ids and a caption with per-platform overrides, and GET /publishing/posts/{id} reports each destination's status and live URL. Connecting a new OAuth account needs a person to open the link in a browser.

Call GET /publishing/accounts, then POST /videos/vid_abc123/publish with account_ids for the TikTok and YouTube accounts and caption 'New feature walkthrough', then poll GET /publishing/posts/{id}

Captioned video exports for other tools

Teams that edit elsewhere can pull the assets out. GET /videos/{id}/download returns a signed MP4 URL, GET /videos/{id}/captions returns the caption file as SRT or VTT through the format parameter, and POST /videos/{id}/share-link creates an expiring public link for reviewers without an account.

Call GET /videos/vid_abc123/captions with format 'vtt', then POST /videos/vid_abc123/share-link with expires_in_seconds 86400

Key Endpoints

65 endpoints — the makeaivideo api turns a brief or your own script into a finished short-form video with script, voiceover, ai or stock scenes, captions, and music, then lets you edit, regenerate, and download the mp4.

METHOD

PATH

DESCRIPTION

GET

/tools

List create tools and their brief fields

POST

/videos/estimate

Get a free credit quote

POST

/videos

Create a video from a brief or script

GET

/videos/{id}

Video status and progress

GET

/videos/{id}/download

Signed download URL for the MP4

POST

/videos/{id}/scenes/{n}/regenerate

Regenerate one scene

POST

/videos/{id}/publish

Post a video to connected accounts

POST

/webhooks

Create a webhook

GET

/tools

List create tools and their brief fields

POST

/videos/estimate

Get a free credit quote

POST

/videos

Create a video from a brief or script

GET

/videos/{id}

Video status and progress

GET

/videos/{id}/download

Signed download URL for the MP4

POST

/videos/{id}/scenes/{n}/regenerate

Regenerate one scene

POST

/videos/{id}/publish

Post a video to connected accounts

POST

/webhooks

Create a webhook

Why Jentic?

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

Setup

Wiring MakeAIVideo by hand means handling its mav_ bearer key with read, write, and ai scopes, polling renders by poll_after_seconds, setting idempotency keys, and verifying signed webhooks yourself. Through Jentic you install once, import MakeAIVideo from the API Directory, store the key once, and your agent calls it.

Permission scoping

MakeAIVideo puts the video id in the URL path for status, edits, downloads, and publishing, so a rule can pin your agent to one video and the operations you pick. You choose the operations it may call, so credit-spending or destructive ones like POST /videos, publishing, or DELETE /videos/{id} are not included unless you add them.

Credential isolation

Your MakeAIVideo 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 video from a script' or 'publish a video to TikTok', and Jentic returns the matching MakeAIVideo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MakeAIVideo API through Jentic.

Is there a MakeAIVideo MCP server?

You don't need an MCP server to give your agent MakeAIVideo. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so the API's many operations do not load as tool definitions into the agent's context.

What authentication does the MakeAIVideo API use?

Per its OpenAPI spec, the MakeAIVideo API uses bearer authentication with a mav_ organization key in the Authorization header. Keys carry read, write, and ai scopes, and each operation lists the scope it needs. The device-login pair used by the CLI takes no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I limit what my agent is allowed to do with MakeAIVideo?

Yes. For example, write a rule that allows GET /videos/vid_abc123, GET /videos/vid_abc123/download, and GET /videos/vid_abc123/captions, so the agent can check and fetch that one video but cannot spend credits on new renders, publish, or delete it. Every call it makes is logged on your own machine.

How do I avoid being charged twice for the same video?

Set idempotency_key on POST /videos so a retried request never produces, or charges for, a second video. POST /videos/{id}/publish also accepts an idempotency_key so a retry never posts twice. Use POST /videos/estimate first for a free credit quote.

How do I create a video through Jentic?

Install Jentic One, import the MakeAIVideo API from the directory, and search for 'create a short video from a brief'. Jentic returns the createVideo operation with its input schema; your agent sends a tool and fields or its own script, then polls GET /videos/{id} until the render is ready. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which social platforms can MakeAIVideo publish to?

Per the spec, finished videos can be posted to TikTok, Instagram as a Reel, YouTube as a Short or regular video, Facebook Pages, LinkedIn, X, Threads, Pinterest, Bluesky, Telegram, and Discord. Connecting an OAuth account requires a person to open the link from POST /publishing/accounts/connect in a browser.

What are the rate limits for the MakeAIVideo API?

The OpenAPI spec does not specify request rate limits. Errors carry a retryable flag that is true only for 5xx and 429 responses. Check https://makeaivideo.ai for current limits.

MakeAIVideo API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo Processingbearer65 EndpointsREST

For Agents

Create short-form videos from a brief or script, regenerate scenes and voiceovers, download the MP4 and captions, and publish finished videos to connected social accounts.

Use for: Make a 30-second explainer video from this product brief, Get a credit quote before rendering a video, Check whether my video has finished rendering, Regenerate scene 3 with new narration

Not supported: Does not handle long-form video editing timelines, live streaming, or video hosting and playback analytics. Use for generating, editing, and publishing short-form AI videos only.

The MakeAIVideo API turns a brief or your own script into a finished short-form video with script, voiceover, AI or stock scenes, captions, and music, then lets you edit, regenerate, and download the MP4. The core loop lists the available create tools, takes a free credit quote, starts a render with an idempotency_key so retries never charge twice, and polls status or waits for a video.ready webhook. Beyond creation it regenerates single scenes or the whole voiceover, exports SRT or VTT captions, manages reusable characters, voices, and music, and publishes finished videos to connected TikTok, Instagram, YouTube, LinkedIn, and other social accounts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

87%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

34%

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: D-Signals: 4

15%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MakeAIVideo API to your agent

Capabilities

Start building with MakeAIVideo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MakeAIVideo API

Jentic AI Readiness Score

MakeAIVideo API

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