Install Jentic One Beta

Connect the FilmeeAi API to your agent

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

Edit a recorded talking-head video with explainer animation that matches the narration

Add burned-in subtitles, skin beautify, and background music to a talking-head video

Generate a narrated anime video from a text prompt

Poll a video job's status for free until it finishes

Fetch the finished video file, with credits charged only on the first successful result

GET STARTED

Start building with FilmeeAi API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use FilmeeAi API for, with concrete tasks.

★ Agent video production through Jentic

An AI agent turns a recorded clip or a script into a finished video without a person babysitting the render. It submits a talking-head edit or an anime generation, polls the job for free until it reports done, then fetches the file, so a content pipeline can produce a video end to end and only spend credits when a result is actually delivered.

Submit a talking-head edit with subtitles enabled, poll the job until done, then fetch the finished file

Explainer and social video from a recording

Creators record themselves and want a polished explainer without an editing suite. The talking-head endpoint adds animation that matches the speech, burned-in subtitles, skin beautify, and background music, so a workflow can take a raw recording and return a share-ready clip.

Edit a recorded talking-head video with subtitles and background music, then retrieve the result

Narrated anime from text

Marketers and educators want short narrated animations without producing them by hand. The anime endpoint takes a text prompt and returns a narrated anime video, so a tool can script a storyline and get back a rendered clip to publish.

Generate a narrated anime video from a short text prompt and fetch the finished file once the job completes

Key Endpoints

5 endpoints — the filmeeai api adds ai video editing to your own app.

METHOD

PATH

DESCRIPTION

GET

/account

Credit balance, plan, and prices

POST

/talk-videos

Edit a recorded talking-head video

POST

/anime-videos

Generate a narrated anime video from text

GET

/videos/{id}

Get a video job's status

POST

/videos/{id}/result

Fetch the finished file (charges credits on the first call)

GET

/account

Credit balance, plan, and prices

POST

/talk-videos

Edit a recorded talking-head video

POST

/anime-videos

Generate a narrated anime video from text

GET

/videos/{id}

Get a video job's status

POST

/videos/{id}/result

Fetch the finished file (charges credits on the first call)

Why Jentic?

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

Setup

Wiring the FilmeeAi API by hand means handling its Bearer token, the asynchronous create-poll-result flow, and the credit accounting where only the first result call charges. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

You choose which operations your agent may call, so it can create jobs and poll their status while the result operation, which charges credits, stays out unless you add it. The account read stays available so the agent can check the balance first.

Credential isolation

Your FilmeeAi token 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 'generate a video from text' or 'edit a talking-head video', and Jentic returns the matching FilmeeAi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using FilmeeAi API through Jentic.

What authentication does the FilmeeAi API use?

It uses a Bearer token sent in the Authorization header, per its OpenAPI spec. The same credential reads your account balance and submits video jobs, and the account endpoint reports the plan and per-job prices so you know the cost before you render.

How does the FilmeeAi API charge for a video?

Every job is asynchronous: you create it, poll its status for free, and then call the result endpoint to fetch the finished file. Credits are consumed only on the first successful result call, so polling status while a job renders costs nothing.

What are the rate limits for the FilmeeAi API?

The OpenAPI spec does not state a request rate limit. Jobs are metered by credits rather than request count, so read the account endpoint for your balance and prices and check the Filmee documentation for any limits before batching renders.

Is there a Filmee MCP server?

You don't need an MCP server to give your agent the FilmeeAi API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the edit, generate, status, and result operations on demand.

Can I limit what my agent is allowed to do with the FilmeeAi API?

Yes. Write a rule that allows the create-job and status operations and the account read, and leave the result operation, which charges credits, off the list unless you add it, so an agent can prepare and track renders while you keep the paid step deliberate. Every call it makes is recorded in your Jentic One audit log.

How do I generate a video with the FilmeeAi API through Jentic?

Search Jentic for 'generate a video from text', add the FilmeeAi API from the directory, and store your token once; your agent then submits the job, polls its status, and fetches the finished file. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Filmee App FilmeeAi API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo Processingbearer5 EndpointsREST

For Agents

Edit recorded talking-head videos or generate narrated anime videos from text through an async job API. Poll status for free, fetch the finished file, and read credit balance and prices.

Use for: Edit a recorded talking-head video with matching animation, Generate a narrated anime video from a script, Check the status of a video job, Get the finished video file for a completed job

Not supported: Does not handle live streaming, video hosting, or voice cloning. Use for AI talking-head video editing and text-to-anime video generation only.

The FilmeeAi API adds AI video editing to your own app. It edits a recorded talking-head video with explainer animation that matches what is said, burned-in subtitles, skin beautify, and background music, and it generates a narrated anime video from a text prompt. Every job is asynchronous: you create it, poll its status for free, then fetch the finished file. Credits are charged only on the first successful result call, and an account endpoint reports the balance, plan, and per-job prices.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

30%

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.

45%

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: 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: A-Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the FilmeeAi API to your agent

Capabilities

Start building with FilmeeAi API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Filmee App FilmeeAi API

Jentic AI Readiness Score

FilmeeAi 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