ApexVerify for AI agents
ApexVerify validates and normalizes email addresses and phone numbers, individually or in batches, so sales and marketing teams can keep contact lists clean before outreach. 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 ApexVerify.
Verify a single contact's email or phone
Check whether one email address or phone number is valid before adding it to a list.
Run a batch verification job
Upload a batch of contacts and launch verification across the entire list at once.
Confirm before deleting a batch
Deleting a verification batch removes its results and should be confirmed before it runs.
10 ApexVerify actions, graded by risk.
Every ApexVerify 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.
- apexverify.list_batchesList Batches
- apexverify.get_batch_detailsGet Batch Details
- apexverify.get_account_creditsGet Account Credits
- apexverify.export_batch_resultsExport Batch Results
- apexverify.verify_email_or_phoneVerify Email or Phone
write
4Create and change things. Allow, or ask the user first.
- apexverify.upload_batchUpload Verification Batch
- apexverify.prepare_batchPrepare Batch
- apexverify.launch_batch_verificationLaunch Batch Verification
- apexverify.normalize_email_or_phone_fileNormalize Data File
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- apexverify.delete_batchDelete Batch
ApexVerify in three steps.
- 01Your users connect ApexVerifyThey add their ApexVerify api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “upload Verification Batch” can wait for the user, and “delete Batch” can be denied outright.
- 03Any agent can actYour agent calls ApexVerify through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('apexverify', { read: 'allow', write: 'ask', // upload_batch destructive: 'deny', // delete_batch }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How ApexVerify connects.
Users add their ApexVerify 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 ApexVerify 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 ApexVerify from any agent.
ApexVerify and Arc0, answered.
Can I use ApexVerify with Claude, ChatGPT or Cursor?
Yes. Connect ApexVerify 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 ApexVerify actions you allow.
How do users connect ApexVerify?
Users add their ApexVerify 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 ApexVerify actions can my agent take?
10 in total: 5 read, 4 write and 1 destructive, such as “upload Verification Batch”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in ApexVerify?
Yes. Actions like “delete Batch” 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 ApexVerify too?
Yes. The same ApexVerify connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug ApexVerify into your agent.
Your users connect ApexVerify 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