Get started

Verifiedemail for AI agents

VerifiedEmail verifies addresses and cleans email lists in bulk, used by marketing teams protecting sender reputation before a campaign sends. 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.

Connect VerifiedemailSee the 9 actions ↓
EmailAPI keyMCP + RESTverifiedemail.com
AUDIT LOG · VERIFIEDEMAILPOLICY: acme-support
09:41:07 · claude · u_8f2read
verifiedemail.list_lists
List Lists✓ allowed · 212ms
09:41:08 · claude · u_8f2read
verifiedemail.verify_email
Verify Email✓ allowed · 164ms
09:41:09 · claude · u_8f2write
verifiedemail.get1_click_user_data
Get 1-Click User Data✓ approved · approved by user
EVERY VERIFIEDEMAIL CALL, ON THE RECORD
01 · USE CASES

What agents do in Verifiedemail.

01

Verify a single email address

Check whether an address is valid before it's added to a send list.

02

Check remaining credits

Read the account's remaining verification credits, a read-only usage check.

03

Check a bulk file's processing status

Look up whether an uploaded list has finished verifying.

02 · ACTIONS

9 Verifiedemail actions, graded by risk.

Every Verifiedemail action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • verifiedemail.list_lists
    List Lists
  • verifiedemail.list_downloads
    List Downloads
  • verifiedemail.get_entitlements
    Get Entitlements
  • verifiedemail.get_shared_credentials
    Get Shared Credentials
  • verifiedemail.verify_email
    Verify Email
  • verifiedemail.check_credits
    Check Credits
  • verifiedemail.check_file_status
    Check File Status

write

2

Create and change things. Allow, or ask the user first.

  • verifiedemail.get1_click_user_data
    Get 1-Click User Data
  • verifiedemail.post1_click_credentials_update
    Update 1-Click Credentials

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Verifiedemail in three steps.

  1. 01Your users connect VerifiedemailThey add their Verifiedemail api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “get 1-Click User Data” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Verifiedemail through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('verifiedemail', {
  read: 'allow',
  write: 'ask',        // get1_click_user_data
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Verifiedemail connects.

Users add their Verifiedemail 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 Verifiedemail 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
05 · WORKS WITH

Use Verifiedemail from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More email apps.

Gmail62 actionsOutlook306 actionsSendGrid364 actionsMixmax94 actionsElastic Email91 actionsResend66 actionsLettr60 actionsPostmark46 actions
ALL EMAIL APPS →
07 · FAQ

Verifiedemail and Arc0, answered.

Q01

Can I use Verifiedemail with Claude, ChatGPT or Cursor?

Yes. Connect Verifiedemail 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 Verifiedemail actions you allow.

Q02

How do users connect Verifiedemail?

Users add their Verifiedemail 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.

Q03

Which Verifiedemail actions can my agent take?

9 in total: 7 read, 2 write and 0 destructive, such as “get 1-Click User Data”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Verifiedemail?

Yes. Allow read actions and deny writes in the Verifiedemail policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Verifiedemail too?

Yes. The same Verifiedemail connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Verifiedemail into your agent.

Your users connect Verifiedemail once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.

Connect VerifiedemailBrowse all apps →

Free to build · MCP + REST · Audit log on every plan