Official vendor OpenAPI document · agent-readyAI/MLSpeechbearer5 EndpointsREST
For Agents
Generate AI voiceovers and text-to-video clips from a script, choosing from Fliki's voice and language catalog.
Use for: Generate a voiceover for this product script in US English, Create a 60-second video from this marketing copy, List all the female voices available in Spanish, Find which dialects are available for the English language
Not supported: Does not handle video editing timelines, live streaming, or transcription - use for AI text-to-speech and text-to-video generation only.
The Fliki API is the Enterprise interface to Fliki's AI text-to-speech and text-to-video platform. It exposes voice, language, and dialect catalogs, and two generation endpoints that turn text into either an audio file or a fully assembled video. The API is intentionally narrow: it covers the discovery of available voices and languages, then the creation of media from a text prompt.
Install Jentic One Beta
Connect the Fliki API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fliki 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.
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%2Ffliki.ai%2Ffliki" | 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%2Ffliki.ai%2Ffliki" | 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 Fliki API.
Generate an AI voiceover from a script using a chosen voice and language
Generate a fully assembled video from a script with synchronized voiceover
List supported languages for text-to-speech and text-to-video generation
List dialects available within a language to fine-tune accent and locale
Browse the catalog of AI voices including gender, style, and language coverage
Pick a voice that matches a target audience before generating media
Use Cases
Patterns agents use Fliki API for, with concrete tasks.
★ Automated marketing video creation
Marketing teams turn written ad copy and product descriptions into short-form videos by posting the script to /generate/video with a chosen voice. Fliki returns a finished MP4 with synchronized voiceover, removing the manual edit step. The same flow scales to localized versions by re-running with a different language or dialect.
Generate a video from a 90-word product script using a US English female voice and return the resulting video URL
Audio version of written content
Publishers and bloggers create audio versions of articles by sending the article text to /generate/audio with a chosen voice. The endpoint returns an MP3 file that can be hosted as a podcast episode or embedded in the original article, expanding accessibility without hiring voice talent.
Generate an audio version of a 1,200-word article using a calm narrative voice and return the MP3 download URL
Localized content in multiple languages
Customer-education and onboarding teams produce localized voiceovers by querying /languages and /dialects for supported locales, then calling /generate/audio or /generate/video for each one. The voice catalog returned by /voices lets the agent choose a regionally appropriate voice for each output.
Pick the most popular female voice for each of fr-FR, es-ES, and de-DE, then generate the same script in all three locales
AI agent narrated explainer
An AI agent that produces written explainers can pipe its output directly into Fliki to deliver narrated audio or video. Through Jentic, the agent searches by intent and gets the right Fliki endpoint and voice catalog without hard-coding API paths, so the same skill works whether the user wants an MP3 or a finished video.
Given a 200-word explainer the agent has just written, generate an MP4 with a male documentary voice in en-US
Key Endpoints
5 endpoints — the fliki api is the enterprise interface to fliki's ai text-to-speech and text-to-video platform.
METHOD
PATH
DESCRIPTION
GET
/languages
List supported languages
GET
/dialects
List supported dialects
GET
/voices
List available AI voices
POST
/generate/audio
Generate an audio voiceover from text
POST
/generate/video
Generate a video with voiceover from text
GET
/languages
List supported languages
GET
/dialects
List supported dialects
GET
/voices
List available AI voices
POST
/generate/audio
Generate an audio voiceover from text
POST
/generate/video
Generate a video with voiceover from text
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Fliki API
- AI-Aware (B)67/100
93
Foundational Compliance63
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
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).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
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.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
32%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
60
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).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Fliki API by hand means setting its bearer auth, looking up language, dialect, and voice IDs before each generation, and handling retries yourself. Through Jentic you install once, import Fliki from the API Directory, store the token once, and your agent calls it.
Permission scoping
Fliki carries its generation target in the request body rather than as an owned resource in the URL path, so limit the agent to the operations it needs, such as listing voices or generating audio, and leave the rest out of the allowed set. You choose which of the five operations it may call.
Credential isolation
Your Fliki token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header 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 'list available voices', and Jentic returns the matching Fliki 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.
FAQs
Specific to using Fliki API through Jentic.
What authentication does the Fliki API use?
The Fliki API uses HTTP bearer tokens issued from a Fliki Enterprise account. Through Jentic the bearer token is held in the encrypted vault and injected into the Authorization header at execution time.
Can I generate a video from a script with the Fliki API?
Yes. POST your script to /generate/video with a chosen voice and Fliki returns a finished MP4 with synchronized voiceover.
How do I choose which voice to use?
Call GET /voices to list available voices with their language, dialect, gender, and style attributes, then pass the chosen voice ID to /generate/audio or /generate/video.
What are the rate limits for the Fliki API?
The Fliki API does not document a fixed rate limit in the spec. Generation throughput depends on your Enterprise plan. Treat 429 responses as the source of truth and back off using the Retry-After header.
How do I generate an AI voiceover through Jentic?
Search Jentic for 'generate an AI voiceover', load the schema for /generate/audio, and execute the call with your script and a chosen voice. Install with pip install jentic and run it through Jentic One, the self-hosted execution layer.
Is the Fliki API free?
API access is part of Fliki's Enterprise tier rather than the standard product. Confirm the current pricing on fliki.ai before integrating.
Can I limit what my agent is allowed to do with the Fliki API?
Yes. Because you run Jentic One yourself, your own rules decide which of Fliki's five operations the agent may call, so you can allow it to list voices, languages, and dialects while blocking the generation endpoints, or permit only /generate/audio and leave /generate/video out. Since Fliki carries its generation target in the request body rather than as a resource in the URL path, scoping is done at the operation level: you grant just the calls the agent needs and withhold the rest. The Fliki bearer token stays with your Jentic One instance and is added to the request only for operations you have allowed.
GET STARTED