Veriphone for AI agents
Veriphone validates phone numbers, returning carrier, type, and region, used by developers checking contact data before it enters a CRM or messaging system. 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 Veriphone.
Verify a phone number
Check whether a phone number is valid and get its carrier and region.
Get an example number for a country
Look up a correctly formatted example number for testing a country's format.
Screen a contact list before import
Check each number in a list of new contacts before they're added to a CRM.
2 Veriphone actions, graded by risk.
Every Veriphone action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- veriphone.get_example_phone_numberGet Example Phone Number
- veriphone.verify_phone_numberVerify Phone Number
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Veriphone in three steps.
- 01Your users connect VeriphoneThey add their Veriphone api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Veriphone through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('veriphone', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Veriphone connects.
Users add their Veriphone 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 Veriphone 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 Veriphone from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Veriphone and Arc0, answered.
Can I use Veriphone with Claude, ChatGPT or Cursor?
Yes. Connect Veriphone 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 Veriphone actions you allow.
How do users connect Veriphone?
Users add their Veriphone 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 Veriphone actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Veriphone?
Yes. Allow read actions and deny writes in the Veriphone policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Veriphone too?
Yes. The same Veriphone connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Veriphone into your agent.
Your users connect Veriphone once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan