Install Jentic One Beta

Connect the Fluen Studio API Reference to your agent

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

Create media by uploading a file or pointing at a URL with transcription and translation specs

Import existing SRT subtitles for translation without uploading any media

Export a caption track in a chosen format or re-import a corrected version

Burn a caption track into a video and fetch the download link

GET STARTED

Start building with Fluen Studio API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Fluen Studio API Reference API for, with concrete tasks.

★ Agent-Driven Media Localization

An AI agent connected through Jentic localises a video end to end: it creates media from the source, requests a transcription and the target-language translations, then exports or burns in the finished captions, so a team ships subtitled video without a manual captioning tool. Because Fluen keeps each language as a track, the agent can add a language later without redoing the transcription.

Create media from this video URL, request an English transcription and French and German translations, then export each track as SRT

Subtitle Translation Without Upload

A workflow that already has SRT files translates them without re-uploading media by importing the subtitles and requesting translations, so an archive of existing captions is localised quickly. Corrected subtitles can be re-imported into an existing track to replace its content and optionally restart the translations in one call.

Import this SRT file, translate it into Japanese, and re-import the corrected version into the existing track

Consistent Terminology Across Languages

A localisation team keeps brand and product terms consistent across every translation by maintaining a workspace term base, adding terms in bulk and exporting it for review, so the same phrase renders the same way in each language. The term base applies to the workspace's translation jobs, so new media inherits the agreed terminology.

Bulk-add our product terms to the workspace term base so every new translation uses the approved wording

Key Endpoints

40 endpoints — the fluen studio api transcribes and translates audio and video and manages the resulting caption tracks, so an application can caption and localise media without running its own speech and translation pipeline.

METHOD

PATH

DESCRIPTION

POST

/api/media

Create media with transcription and translation specs

POST

/api/media/from-captions

Create media from imported captions (SRT)

GET

/api/media/{mediaId}

Read a media item

GET

/api/tracks/{trackId}

Read a caption track

GET

/api/tracks/{trackId}/export/{format}

Export a caption track in a format

POST

/api/tracks/{trackId}/import

Import and replace track content

POST

/api/tracks/{trackId}/burnin/{videoFormat}

Burn a caption track into a video

POST

/api/webhook-endpoints

POST

/api/media

Create media with transcription and translation specs

POST

/api/media/from-captions

Create media from imported captions (SRT)

GET

/api/media/{mediaId}

Read a media item

GET

/api/tracks/{trackId}

Read a caption track

GET

/api/tracks/{trackId}/export/{format}

Export a caption track in a format

POST

/api/tracks/{trackId}/import

Import and replace track content

POST

/api/tracks/{trackId}/burnin/{videoFormat}

Burn a caption track into a video

POST

/api/webhook-endpoints

Why Jentic?

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

Setup

Wiring the Fluen Studio API by hand means handling X-API-Key auth, picking between uploading media and creating it from a URL or captions, and tracking each transcription and translation job to completion. Through Jentic you install once, import Fluen from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which operations your agent may call, so you can allow creating media and exporting tracks while leaving destructive ones like deleting media or clearing the term base out. Rules bound which operations run, so the agent captions and translates and cannot reach anything you did not grant.

Credential isolation

Your Fluen 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 'transcribe and translate a video' or 'export a caption track', and Jentic returns the matching Fluen operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Fluen Studio API Reference API through Jentic.

Is there a Fluen MCP server?

You don't need an MCP server to give your agent the Fluen Studio API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can transcribe, translate, and export caption tracks straight away, with no extra server to run and no tool definitions sitting in the agent's context.

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

Yes. Write a rule that allows only the operations the agent needs, such as creating media and exporting tracks, and leave deletions out. Every call the agent makes is logged, so you can see exactly which media and tracks it created.

What authentication does the Fluen Studio API use?

The Fluen Studio API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can I translate subtitles without uploading media to the Fluen Studio API?

Yes. One operation creates media directly from captions, so you can import an existing SRT file and request translations without uploading any audio or video. A separate operation re-imports a corrected track to replace its content and optionally restart the translations.

What are the rate limits for the Fluen Studio API?

The OpenAPI spec does not state request rate limits for the Fluen Studio API. For current limits and fair-use guidance, check the provider documentation at https://api.fluen.ai.

How do I caption a video through Jentic?

Import the Fluen Studio API from the Jentic API Directory, then have your agent issue a request such as 'transcribe and translate this video'. Jentic matches the intent to the create-media operation and returns its input schema so the agent builds the correct request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Fluen Studio API Reference

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey40 EndpointsREST

For Agents

Upload audio or video for transcription and translation, import and export subtitle tracks, burn captions into video, and manage a term base in Fluen Studio. Authenticates with an API key in the X-API-Key header.

Use for: Upload a video and request a transcription plus a Spanish translation, Import an SRT file and translate it into several languages, Export a finished caption track as an SRT file, Burn the translated captions into the source video

Not supported: Does not host or stream video, generate voiceovers, or edit footage. Use for transcription, translation, and caption-track management only.

The Fluen Studio API transcribes and translates audio and video and manages the resulting caption tracks, so an application can caption and localise media without running its own speech and translation pipeline. You create media by uploading a file or pointing at a URL, attach transcription and translation job specifications, or import existing SRT subtitles for translation without any upload. Finished caption tracks can be exported in a chosen format, re-imported after outside correction, or burned into a video, and webhook endpoints notify your systems as jobs complete.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 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).

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: CSignals: 4

Example Density

How richly the API is illustrated with examples.

93%

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

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

55%

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Fluen Studio API Reference to your agent

Capabilities

Start building with Fluen Studio API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Fluen Studio API Reference

Jentic AI Readiness Score

Fluen Studio API Reference

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