2chat for AI agents
2Chat is a programmable API for WhatsApp and other text channels, letting developers send and receive messages and manage contacts. It is used to add messaging into apps and workflows. 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 2chat.
Look up existing contacts
List the WhatsApp contacts already stored in the account before deciding whether to add a new one.
Add a new contact
Create a new WhatsApp contact record, a write action added to the account's contact list.
Check API usage
Review how many messages or API calls have been used this period before running a new campaign.
5 2chat actions, graded by risk.
Every 2chat 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.
- 2chat.list_contactsList Contacts
- 2chat.list_webhooksList Webhook Subscriptions
- 2chat.get_api_usage_infoGet API Usage Info
- 2chat.test_api_keyTest API Key
write
1Create and change things. Allow, or ask the user first.
- 2chat.create_contactCreate Contact
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
2chat in three steps.
- 01Your users connect 2chatThey add their 2chat api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Contact” can wait for the user to approve.
- 03Any agent can actYour agent calls 2chat through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('2chat', { read: 'allow', write: 'ask', // create_contact destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How 2chat connects.
Users add their 2chat 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 2chat 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 2chat from any agent.
2chat and Arc0, answered.
Can I use 2chat with Claude, ChatGPT or Cursor?
Yes. Connect 2chat 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 2chat actions you allow.
How do users connect 2chat?
Users add their 2chat 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 2chat actions can my agent take?
5 in total: 4 read, 1 write and 0 destructive, such as “create Contact”. Your policies decide which of them each agent may call.
Can I make my agent read-only in 2chat?
Yes. Allow read actions and deny writes in the 2chat policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call 2chat too?
Yes. The same 2chat connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug 2chat into your agent.
Your users connect 2chat 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