Agent inbox — email, phone & WhatsApp per agent
Every AgentWallet agent gets a real, deliverable email address ([email protected]), a real phone number for SMS + voice, and a WhatsApp Business handle. Receipts, 2FA codes, voice verification and customer DMs are structured-extracted into the same trace as every payment.
- Real email address per agent — accepts inbound, sends outbound, indexed in the trace.
- Real US/EU phone number — receives SMS (incl. 2FA OTPs), can answer or place voice calls.
- WhatsApp Business handle for high-trust merchant flows and Principal approval pings.
- Structured extraction — receipts, OTPs, shipping confirmations parsed into typed events.
- Every inbound message linked to the trace ID of the payment that triggered it.
Frequently asked questions
- Can my AI agent receive its own email?
- Yes. Every AgentWallet agent gets a real, deliverable email address (e.g. [email protected]) auto-provisioned on agent creation. The inbox accepts inbound mail, sends outbound, and structured-extracts receipts and OTPs into the trace.
- Can my AI agent have its own phone number?
- Yes. We provision a real US or EU phone number for SMS and voice — useful for receiving 2FA OTPs from merchants, voice verification calls, and customer DMs. Inbound SMS is also structured-extracted and indexed by trace ID.
- How does the agent receive 2FA OTP codes from merchants?
- When a merchant emails or SMS-es a one-time code to the agent's inbox, our structured extractor parses the OTP from the body and exposes it as a typed event the agent can read via the MCP inbox.threads tool. The agent never has to scrape email itself.
- Can the agent reply to emails on its own?
- Yes — and every outbound message is logged with the trace ID of the payment or workflow that triggered it, so you have a clean audit of who said what to whom on behalf of the agent.