Skip to main content
A messaging agent lives where your users already chat — iMessage, WhatsApp, Slack, Telegram, SMS and RCS, or your own web chat — and pays for things with Agentcard on their behalf. The user texts, the agent shops, an Agentcard virtual card settles it.

​
Example messaging agents

Poke

Poke logo

Orchid

Orchid logo

Tomo

Tomo logo

​
The expected flow

  1. Create your organization and OAuth client. Install the admin CLI, create your org, and register an OAuth client — that gives you your client ID and secret.
  2. Authenticate each user with OAuth. The first time a user talks to your agent, hand them a Connect with Agentcard link in the conversation. They verify by email and approve once — you get their access and refresh tokens.
  3. Implement the MCP server in your agent. Point your agent’s MCP client at the Agentcard MCP server and register every tool it advertises.
  4. Make requests with the user’s token. Each tool call carries that user’s access token — the cards your agent creates are isolated to your app and that user, funded from their own wallet.

​
Start from an example

Every example in the Examples section implements exactly this flow, end to end, on a different messaging surface. Building on Photon? Start from the Photon example. Sending over Twilio SMS? The Twilio example has the same wiring. Sendblue, LoopMessage, Linq, BlueBubbles, Respond.io, Hermes, and the Vercel Chat SDK are covered too — clone the closest one and adapt. Or skip the reading: the wizard implements this flow into your repo directly.