MuAPI for AI agents
MuAPI is an OpenAI-compatible API for generating images and discovering which image generation models are supported, letting teams switch models easily. 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 MuAPI.
Generate an image from a prompt
Create a draft image from a text prompt for a creative concept.
Check available models
List the models supported through the catalog before choosing one for a job, read-only.
Estimate cost before generating
Estimate the cost of an image generation request before submitting it, so spend stays predictable.
5 MuAPI actions, graded by risk.
Every MuAPI action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- muapi.list_modelsList Models
- muapi.get_catalog_modelGet Catalog Model
- muapi.list_catalog_modelsList Catalog Models
- muapi.estimate_model_costEstimate Model Cost
write
1Create and change things. Allow, or ask the user first.
- muapi.generate_imageGenerate Image
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
MuAPI in three steps.
- 01Your users connect MuAPIThey add their MuAPI api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “generate Image” can wait for the user to approve.
- 03Any agent can actYour agent calls MuAPI through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('muapi', { read: 'allow', write: 'ask', // generate_image destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How MuAPI connects.
Users add their MuAPI 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 MuAPI 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 MuAPI from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
MuAPI and Arc0, answered.
Can I use MuAPI with Claude, ChatGPT or Cursor?
Yes. Connect MuAPI 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 MuAPI actions you allow.
How do users connect MuAPI?
Users add their MuAPI 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 MuAPI actions can my agent take?
5 in total: 4 read, 1 write and 0 destructive, such as “generate Image”. Your policies decide which of them each agent may call.
Can I make my agent read-only in MuAPI?
Yes. Allow read actions and deny writes in the MuAPI policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call MuAPI too?
Yes. The same MuAPI connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug MuAPI into your agent.
Your users connect MuAPI once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan