Zoho is opening early access to AgentInbox, email infrastructure built for AI agents. Each agent gets its own mailbox, credentials and activity log, which helps teams that need agents to send and receive email without borrowing a human's inbox.
Why agents need their own email
Agents that do real work often need email. The usual workarounds are sharing a human's inbox or using a forwarded alias. Both blur accountability, complicate audit trails and make it difficult to revoke access.
What AgentInbox does
Zoho AgentInbox provisions a dedicated mailbox with a permanent address, isolated credentials and a cross-session action log. It is built for programmatic use. Mailboxes are provisioned through code, credentials are issued per agent and every capability is exposed through a REST API.
Capabilities at a glance
| Area | What you get |
|---|---|
| An address it owns | Mailboxes provisioned at runtime for a user, workflow or task and removed when no longer needed. Mail arrives as threaded conversations with attachments available on arrival. |
| Delivery | SPF and DKIM authentication, isolated sending domains and real-time reporting of bounces, spam complaints and failures. |
| Event-driven | Events for new messages, replies and delivery failures are pushed to your endpoint. Subscriptions are granular, payloads are HMAC-signed and failed deliveries retry automatically with each attempt logged. |
| Credentials | One API key per agent, so keys can be revoked individually. OAuth with automatically rotating tokens for user-delegated cases. Data is encrypted with AES-256. |
| Integration | A REST API for all capabilities and a built-in MCP server for MCP-compatible frameworks. Python and Node.js SDKs and a CLI are listed as coming soon. |
| Audit trail | Full delivery tracing from queue to open or bounce, logging of every API call (payload, response, latency and key used), webhook replay that does not re-trigger live actions and a dashboard for volume, delivery health and webhook performance. |
Two example use cases
- Sales outreach. A sales agent runs outreach from its own address. Replies go directly to it, and every message is logged.
- Customer onboarding. An onboarding agent handles inbound mail with full thread context. Customers do not repeat themselves, and escalations arrive with context.
Roadmap and early access
Contacts and Calendar APIs are in development, so agents will be able to book meetings and manage records. Expanded channels such as SMS and voice are coming soon.
You can sign up for early access and check the AgentInbox pricing page. Zoho invites feedback in the blog comments.
Questions
What is Zoho AgentInbox?
It is email infrastructure for AI agents. Each agent gets its own mailbox, credentials and activity log.
Why not give an agent a shared inbox or a forwarded alias?
Those workarounds blur accountability, complicate audit trails and make it difficult to revoke access.
How are agent credentials handled?
Each agent has its own API key, so keys can be revoked individually. OAuth with automatically rotating tokens is available for user-delegated cases, and data is encrypted with AES-256.
How do I connect AgentInbox to my agent framework?
Use the REST API, which covers all capabilities, or the built-in MCP server for MCP-compatible frameworks.
What is coming next?
Contacts and Calendar APIs are in development. Python and Node.js SDKs, a CLI and channels such as SMS and voice are listed as coming soon.
Based on Introducing Zoho AgentInbox: Email infrastructure built for AI Agents on the Zoho Blog.