Bannerbite for AI agents
Bannerbite is a creative automation tool that turns reusable projects and templates into finished images and videos, used by marketing teams to produce on-brand assets quickly. 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 Bannerbite.
Generate a video from a project
Generate media from a saved project and scene data to produce a new on-brand video ad.
Check a project's scene data
Pull the scene data for a project to confirm the layout before generating new assets from it.
Avoid regenerating an asset
List existing bites in a project as a read-only check to avoid regenerating an asset that already exists.
6 Bannerbite actions, graded by risk.
Every Bannerbite 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.
- bannerbite.get_biteGet Bite
- bannerbite.list_bitesList Bites
- bannerbite.get_projectGet Project
- bannerbite.list_projectsList Projects
- bannerbite.get_scene_dataGet Scene Data
write
1Create and change things. Allow, or ask the user first.
- bannerbite.generate_mediaGenerate Media
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Bannerbite in three steps.
- 01Your users connect BannerbiteThey add their Bannerbite api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “generate Media” can wait for the user to approve.
- 03Any agent can actYour agent calls Bannerbite through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bannerbite', { read: 'allow', write: 'ask', // generate_media destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Bannerbite connects.
Users add their Bannerbite 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 Bannerbite 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 Bannerbite from any agent.
Bannerbite and Arc0, answered.
Can I use Bannerbite with Claude, ChatGPT or Cursor?
Yes. Connect Bannerbite 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 Bannerbite actions you allow.
How do users connect Bannerbite?
Users add their Bannerbite 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 Bannerbite actions can my agent take?
6 in total: 5 read, 1 write and 0 destructive, such as “generate Media”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Bannerbite?
Yes. Allow read actions and deny writes in the Bannerbite policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Bannerbite too?
Yes. The same Bannerbite connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Bannerbite into your agent.
Your users connect Bannerbite 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