Inworld AI for AI agents
Inworld AI provides speech synthesis, speech recognition, and voice management for building conversational voice experiences. Teams building AI products use it to add this capability without training or hosting their own model. 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 Inworld AI.
Synthesize speech from text
Convert a script into spoken audio using a chosen voice for a character or narration.
Transcribe an audio clip
Transcribe a recorded audio clip into text for review or captioning.
List available voices
List available voices to pick the right one for a new interactive character.
6 Inworld AI actions, graded by risk.
Every Inworld AI action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- inworld_ai.list_modelsList Models
- inworld_ai.list_voicesList Voices
- inworld_ai.get_voice_previewGet Voice Preview
write
3Create and change things. Allow, or ask the user first.
- inworld_ai.create_embeddingsCreate Embeddings
- inworld_ai.transcribe_audioTranscribe Audio
- inworld_ai.synthesize_speechSynthesize Speech
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Inworld AI in three steps.
- 01Your users connect Inworld AIThey add their Inworld AI api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Embeddings” can wait for the user to approve.
- 03Any agent can actYour agent calls Inworld 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('inworld_ai', { read: 'allow', write: 'ask', // create_embeddings destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Inworld AI connects.
Users add their Inworld 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 Inworld 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 Inworld AI from any agent.
Inworld AI and Arc0, answered.
Can I use Inworld AI with Claude, ChatGPT or Cursor?
Yes. Connect Inworld 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 Inworld AI actions you allow.
How do users connect Inworld AI?
Users add their Inworld 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 Inworld AI actions can my agent take?
6 in total: 3 read, 3 write and 0 destructive, such as “create Embeddings”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Inworld AI?
Yes. Allow read actions and deny writes in the Inworld AI policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Inworld AI too?
Yes. The same Inworld AI connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Inworld AI into your agent.
Your users connect Inworld AI once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan