Bouncer for AI agents
Bouncer is an email verification service that marketing teams use to check whether addresses are deliverable before sending campaigns, one at a time or in bulk. 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 Bouncer.
Verify a single email address
Run a real-time check on one email address to confirm it is deliverable before it gets used.
Run a bulk verification batch
Create a batch request to verify a list of addresses after the user confirms the credit cost.
Require approval before deleting a batch
Treat deleting a batch or toxicity list job as destructive since it removes verification history.
10 Bouncer actions, graded by risk.
Every Bouncer 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.
- bouncer.get_creditsGet Credits
- bouncer.get_batch_resultsGet Batch Results
- bouncer.verify_emailVerify Email
- bouncer.verify_domainVerify Domain
- bouncer.check_toxicity_list_job_statusCheck Toxicity List Job Status
write
3Create and change things. Allow, or ask the user first.
- bouncer.create_batch_requestCreate Batch Request
- bouncer.create_toxicity_list_jobCreate Toxicity List Job
- bouncer.finish_batchFinish Batch
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- bouncer.delete_batch_requestDelete batch request
- bouncer.delete_toxicity_list_jobDelete Toxicity List Job
Bouncer in three steps.
- 01Your users connect BouncerThey add their Bouncer api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Batch Request” can wait for the user, and “delete batch request” can be denied outright.
- 03Any agent can actYour agent calls Bouncer through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bouncer', { read: 'allow', write: 'ask', // create_batch_request destructive: 'deny', // delete_batch_request }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Bouncer connects.
Users add their Bouncer 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 Bouncer 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 Bouncer from any agent.
Bouncer and Arc0, answered.
Can I use Bouncer with Claude, ChatGPT or Cursor?
Yes. Connect Bouncer 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 Bouncer actions you allow.
How do users connect Bouncer?
Users add their Bouncer 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 Bouncer actions can my agent take?
10 in total: 5 read, 3 write and 2 destructive, such as “create Batch Request”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Bouncer?
Yes. Actions like “delete batch request” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Bouncer too?
Yes. The same Bouncer connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Bouncer into your agent.
Your users connect Bouncer once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan