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.

CRMAPI keyMCP + RESTapexverify.io
AUDIT LOG · APEXVERIFYPOLICY: acme-support
09:41:07 · claude · u_8f2read
apexverify.list_batches
List Batches✓ allowed · 212ms
09:41:08 · claude · u_8f2read
apexverify.get_batch_details
Get Batch Details✓ allowed · 164ms
09:41:09 · claude · u_8f2write
apexverify.upload_batch
Upload Verification Batch✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
apexverify.delete_batch
Delete Batch✕ blocked · policy: deny
EVERY APEXVERIFY CALL, ON THE RECORD
01 · USE CASES

What agents do in ApexVerify.

01

Verify a single contact's email or phone

Check whether one email address or phone number is valid before adding it to a list.

02

Run a batch verification job

Upload a batch of contacts and launch verification across the entire list at once.

03

Confirm before deleting a batch

Deleting a verification batch removes its results and should be confirmed before it runs.

02 · ACTIONS

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

5

Look things up. Allowed by default.

  • apexverify.list_batches
    List Batches
  • apexverify.get_batch_details
    Get Batch Details
  • apexverify.get_account_credits
    Get Account Credits
  • apexverify.export_batch_results
    Export Batch Results
  • apexverify.verify_email_or_phone
    Verify Email or Phone

write

4

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

  • apexverify.upload_batch
    Upload Verification Batch
  • apexverify.prepare_batch
    Prepare Batch
  • apexverify.launch_batch_verification
    Launch Batch Verification
  • apexverify.normalize_email_or_phone_file
    Normalize Data File

destructive

1

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

  • apexverify.delete_batch
    Delete Batch
03 · HOW IT WORKS

ApexVerify in three steps.

  1. 01Your users connect ApexVerifyThey add their ApexVerify api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “upload Verification Batch” can wait for the user, and “delete Batch” can be denied outright.
  3. 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.
POLICY.TS
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
04 · AUTH AND DATA

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
05 · WORKS WITH

Use ApexVerify from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

ApexVerify and Arc0, answered.

Q01

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.

Q02

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.

Q03

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.

Q04

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.

Q05

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.

Get started

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