Resend for AI agents
Resend is a developer-focused email API for sending transactional and marketing email, managing domains, audiences, contacts, and templates. 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 Resend.
Send a broadcast to a segment
Create a draft broadcast for a segment of contacts before it goes out to their inboxes.
Check a domain's setup
Get a domain's verification status before relying on it to send email.
Confirm before deleting an audience
Look up an audience's contacts first, then delete the audience only after confirming it's unused.
66 Resend actions, graded by risk.
Every Resend action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
29Look things up. Allowed by default.
- resend.get_topicGet Topic
- resend.get_contactGet Contact
- resend.get_segmentGet Segment
- resend.get_webhookGet Webhook
- resend.list_emailsList Emails
- resend.list_topicsList Topics
- resend.get_templateGet Template
- resend.list_domainsList Domains
- resend.get_broadcastGet Broadcast
- resend.list_api_keysList API Keys
- resend.list_contactsList Contacts
- resend.list_segmentsList Segments
- resend.list_webhooksList Webhooks
- resend.list_audiencesList Audiences
- resend.list_templatesList Templates
- resend.list_broadcastsList Broadcasts
write
25Create and change things. Allow, or ask the user first.
- resend.send_emailSend Email
- resend.create_topicCreate Topic
- resend.update_emailUpdate Email
- resend.update_topicUpdate Topic
- resend.create_domainCreate Domain
- resend.update_domainUpdate Domain
- resend.create_api_keyCreate API Key
- resend.create_contactCreate Contact
- resend.create_segmentCreate Segment
- resend.create_webhookCreate Webhook
- resend.update_contactUpdate Contact
- resend.update_webhookUpdate Webhook
- resend.create_audienceCreate Audience
- resend.create_templateCreate Template
- resend.update_templateUpdate Template
- resend.update_broadcastUpdate Broadcast
destructive
12Delete, cancel or archive. Ask first, or deny outright.
- resend.cancel_emailCancel Email
- resend.delete_topicDelete Topic
- resend.delete_domainDelete Domain
- resend.delete_api_keyDelete API Key
- resend.delete_contactDelete Contact
- resend.delete_segmentDelete Segment
- resend.delete_webhookDelete Webhook
- resend.delete_audienceDelete Audience
- resend.delete_templateDelete Template
- resend.delete_contact_by_idDelete Contact By ID
- resend.delete_contact_propertyDelete Contact Property
- resend.remove_contact_from_segmentRemove Contact From Segment
Resend in three steps.
- 01Your users connect ResendThey add their Resend api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Topic” can wait for the user, and “delete Topic” can be denied outright.
- 03Any agent can actYour agent calls Resend through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('resend', { read: 'allow', write: 'ask', // create_topic destructive: 'deny', // delete_topic }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Resend connects.
Users add their Resend 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 Resend 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 Resend from any agent.
Resend and Arc0, answered.
Can I use Resend with Claude, ChatGPT or Cursor?
Yes. Connect Resend 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 Resend actions you allow.
How do users connect Resend?
Users add their Resend 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 Resend actions can my agent take?
66 in total: 29 read, 25 write and 12 destructive, such as “create Topic”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Resend?
Yes. Actions like “delete Topic” 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 Resend too?
Yes. The same Resend connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Resend into your agent.
Your users connect Resend once, under your brand. Your agent gets 66 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan