Imejis.io for AI agents
Imejis.io is an API-based image generation platform that creates images from a library of customizable templates. Design and marketing teams use it to produce this asset without a manual editing pass. 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 Imejis.io.
Browse image templates
List the available templates to choose one that fits a new social media graphic.
Compare templates before choosing
Review template options side by side, read-only, before committing to one for a campaign.
Confirm template fit for brand
Check a template's layout details to confirm it matches brand guidelines before use.
1 Imejis.io actions, graded by risk.
Every Imejis.io action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- imejis_io.list_designsList Design Templates
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Imejis.io in three steps.
- 01Your users connect Imejis.ioThey add their Imejis.io api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Imejis.io through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('imejis_io', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Imejis.io connects.
Users add their Imejis.io 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 Imejis.io 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 Imejis.io from any agent.
Imejis.io and Arc0, answered.
Can I use Imejis.io with Claude, ChatGPT or Cursor?
Yes. Connect Imejis.io 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 Imejis.io actions you allow.
How do users connect Imejis.io?
Users add their Imejis.io 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 Imejis.io actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Imejis.io?
Yes. Allow read actions and deny writes in the Imejis.io policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Imejis.io too?
Yes. The same Imejis.io connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Imejis.io into your agent.
Your users connect Imejis.io once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan