Emailable for AI agents
Emailable is an email verification API that checks addresses in real time to keep sending lists accurate and deliverable, used by marketing teams protecting their sender reputation. 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 Emailable.
Verify an email address
Verify a single email address before it is added to an outbound campaign list.
Check a batch verification job
Get a batch job's status to see whether a bulk list verification has completed.
Read-only account info checks
Get account info to check remaining verification credits before running a large batch.
5 Emailable actions, graded by risk.
Every Emailable 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.
- emailable.get_account_infoGet Account Info
- emailable.get_batch_statusGet Batch Status
- emailable.verify_emailVerify Email
- emailable.verify_batch_emailsVerify Batch Emails
write
1Create and change things. Allow, or ask the user first.
- emailable.o_auth_authorizeBuild OAuth Authorization URL
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Emailable in three steps.
- 01Your users connect EmailableThey add their Emailable api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “build OAuth Authorization URL” can wait for the user to approve.
- 03Any agent can actYour agent calls Emailable through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('emailable', { read: 'allow', write: 'ask', // o_auth_authorize destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Emailable connects.
Users add their Emailable 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 Emailable 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 Emailable from any agent.
Emailable and Arc0, answered.
Can I use Emailable with Claude, ChatGPT or Cursor?
Yes. Connect Emailable 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 Emailable actions you allow.
How do users connect Emailable?
Users add their Emailable 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 Emailable actions can my agent take?
5 in total: 4 read, 1 write and 0 destructive, such as “build OAuth Authorization URL”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Emailable?
Yes. Allow read actions and deny writes in the Emailable policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Emailable too?
Yes. The same Emailable connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Emailable into your agent.
Your users connect Emailable 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