CAMB.AI API

Name: CAMB.AI API
Brand: CAMB.AI API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLSpeechapiKey10 EndpointsREST

For Agents

Generate speech, dub video, transcribe audio, translate text, and synthesize voices and sound effects across 140+ languages.

Install Jentic One Beta

Connect the CAMB.AI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CAMB.AI 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 CAMB.AI API.

Synthesize streaming text-to-speech audio in 140+ languages via /tts-stream

Translate text and synthesize the result in a target voice via /translated-tts

Run end-to-end video dubbing with voice cloning and lip context via /dub

GET STARTED

Start building with CAMB.AI API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for CAMB.AI API, keeping it validated and agent-ready. CAMB.AI is an AI audio platform covering text-to-speech, dubbing, transcription, translation, voice generation from descriptions, sound and music generation, story narration, and source separation across 140+ languages. Ten POST endpoints expose each capability as a discrete job, including end-to-end video dubbing, translated text-to-speech, and stem separation, making it suited for media localisation, podcasting, and creative-tool agents.

Use Cases

Patterns agents use CAMB.AI API for, with concrete tasks.

★ Video Dubbing for Global Distribution

Media teams localising video for international audiences need to replace the original voice track with translated dialogue while keeping the speaker's vocal identity. The /dub endpoint runs an end-to-end pipeline that translates, voices, and aligns dubbed audio in 140+ target languages, removing the need to chain separate transcription, translation, and TTS calls.

Send POST /dub with a source video URL and target_language='es', then poll the returned run ID until the dubbed audio file is ready.

Multilingual Podcast Production

Podcast networks producing content in multiple languages can chain CAMB.AI endpoints in a single workflow. /transcribe converts the original episode to text, /translate produces the localised script, and /tts-stream or /translated-tts generates the localised audio in the chosen voice, cutting localisation effort to minutes per episode.

Call /transcribe on the episode MP3, /translate the result to French, then /translated-tts with voice_id and the French text to render the localised audio.

Generative Audio for Creative Tools

Creative apps that build voiceovers, audiobooks, and game audio need on-demand voice and sound generation. /text-to-voice creates a custom voice from a text description, /text-to-sound generates sound effects or music from a prompt, and /story narrates structured story content with consistent character voices.

Send POST /text-to-voice with description='warm male storyteller in his 50s', then use the returned voice_id in /story to narrate a five-paragraph children's tale.

AI Agent Audio Workflows via Jentic

Through Jentic, an agent searches for 'dub a video into another language', loads the /dub input schema, and executes the call without managing the x-api-key header. Long-running jobs return run IDs that the agent can poll through subsequent Jentic-mediated calls.

Use the Jentic SDK to search 'dub a video', load the /dub operation schema, and execute it with a video URL and target language to start a dubbing run.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for camb.

METHOD

PATH

DESCRIPTION

POST

/tts-stream

Streaming text-to-speech synthesis

POST

/dub

End-to-end video or audio dubbing

POST

/transcribe

Transcribe audio to text

POST

/translate

Translate text between supported languages

POST

/text-to-voice

Generate a custom voice from a description

POST

/text-to-sound

Generate sound effects or music from a prompt

POST

/audio-separation

Separate vocals from instrumentals or other stems

POST

/tts-stream

Streaming text-to-speech synthesis

POST

/dub

End-to-end video or audio dubbing

POST

/transcribe

Transcribe audio to text

POST

/translate

Translate text between supported languages

POST

/text-to-voice

Generate a custom voice from a description

Why Jentic?

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

Credential isolation

The CAMB.AI API key is stored encrypted in the Jentic vault. Agents receive scoped execution rights and Jentic injects the key into the x-api-key header at call time, so the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (for example, 'dub a video') and Jentic returns the matching CAMB.AI operation along with its input schema, so the agent can call /dub, /transcribe, or /tts-stream without browsing the docs.

Time to first call

Direct CAMB.AI integration: one to two days for auth, async job polling, and media handling. Through Jentic: under 90 minutes to search, load, and execute.

FAQs

Specific to using CAMB.AI API through Jentic.

Why is there no official OpenAPI spec for CAMB.AI API?

CAMB.AI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CAMB.AI 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 CAMB.AI API use?

It uses an API key passed in the x-api-key HTTP header. Through Jentic, the key is stored in the Jentic vault and injected into the x-api-key header at execution time, so the raw key never enters the agent's prompt context.

Can I dub a video end-to-end with one call?

Yes. POST /dub accepts a source media reference and target language and runs transcription, translation, and voicing as a single asynchronous job. The response includes a run ID that you poll to retrieve the dubbed media when processing completes.

How do I transcribe and translate a podcast through Jentic?

Use the Jentic SDK to search 'transcribe and translate audio'. Jentic returns the /transcribe and /translate operations with their input schemas. Execute /transcribe with the audio URL, then pass the returned text into /translate with the target language.

What languages does the API support?

CAMB.AI advertises support for 140+ languages across speech synthesis, dubbing, and translation. Pass the target language code in the request body for /translated-tts, /dub, or /translate; check the CAMB.AI docs for the full ISO code list.

Are jobs synchronous or asynchronous?

Long-running operations such as /dub, /story, and /translated-story/{run_id} are asynchronous and return a run ID. Poll the run-specific endpoint with that ID until the job reports completion before downloading the resulting media.

CAMB.AI API

Connect the CAMB.AI API to your agent

Capabilities

Start building with CAMB.AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs