CAMB.AI for AI agents
CAMB.AI hosts APIs for dubbing, voice cloning, transcription, and translation, letting a team turn audio and video into other languages without a studio. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in CAMB.AI.
Dub a video into another language
Dub a video's audio track into a target language while keeping the original voice's tone.
Transcribe recorded audio
Transcribe a media file into text before it gets translated or repurposed as subtitles.
Check a dubbing job's status
Check a long-running dub or translation task's status before it gets pulled into a project.
8 CAMB.AI actions, graded by risk.
Every CAMB.AI action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- camb_ai.list_voicesList Voices
- camb_ai.get_run_resultGet Run Result
- camb_ai.list_languagesList Supported Languages
- camb_ai.get_task_statusGet Task Status
- camb_ai.translate_textTranslate Text
write
3Create and change things. Allow, or ask the user first.
- camb_ai.dub_mediaDub Media
- camb_ai.transcribe_mediaTranscribe Media
- camb_ai.generate_subtitlesGenerate Subtitles
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
CAMB.AI in three steps.
- 01Your users connect CAMB.AIThey add their CAMB.AI api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “dub Media” can wait for the user to approve.
- 03Any agent can actYour agent calls CAMB.AI through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('camb_ai', { read: 'allow', write: 'ask', // dub_media destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How CAMB.AI connects.
Users add their CAMB.AI api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same CAMB.AI connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use CAMB.AI from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
CAMB.AI and Arc0, answered.
Can I use CAMB.AI with Claude, ChatGPT or Cursor?
Yes. Connect CAMB.AI to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the CAMB.AI actions you allow.
How do users connect CAMB.AI?
Users add their CAMB.AI api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which CAMB.AI actions can my agent take?
8 in total: 5 read, 3 write and 0 destructive, such as “dub Media”. Your policies decide which of them each agent may call.
Can I make my agent read-only in CAMB.AI?
Yes. Allow read actions and deny writes in the CAMB.AI policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call CAMB.AI too?
Yes. The same CAMB.AI connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug CAMB.AI into your agent.
Your users connect CAMB.AI once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan