NetEase has launched an email service built for AI agents — ClawEmail. The product gives AI agents an independent email identity so that any user can interact with an agent by simply sending it an email: no account registration, no app installation, no API integration. The recipient’s experience is deliberately ordinary — composing a message to an address, the way email has worked for fifty years.
ClawEmail’s founding idea is stated plainly: email is the simplest way to invoke an agent. Send a message to the agent’s mailbox; the agent processes it automatically and replies with the result. The whole exchange is transparent to the sender — the other side never even needs to know ClawEmail exists.
Three Steps to an Agent Mailbox
The setup flow is deliberately minimal. Step one, create the mailbox — a single command or a dashboard registration provisions a real @claw.163.com address. Step two, bind the agent — one-click configuration forwards incoming mail content to your designated AI agent, and the processing result is automatically emailed back to the sender. Step three, share the address and go — anyone, using any mailbox they already have (Gmail, QQ Mail, a corporate account), sends an email and the agent responds.
A Programmable Mail-Processing Engine
ClawEmail is more than a mailbox — it is a programmable mail-processing engine, shipping a complete mail API and a command-line tool called mail-cli with these core capabilities:
- Sending and receiving — a full @claw.163.com identity with rich-text bodies, multiple recipients, and CC/BCC
- Body extraction — one command returns clean plain text, ready to feed a model or write to a database
- Attachment handling — receive, download, and send attachments out of the box: PDF, Excel, images, any file type, up to 30MB per message
- Mail search — combined filtering by keyword, sender, and read status, with full-text search over bodies once enabled
- Mail management — batch move, archive, and mark read/unread; the message lifecycle is fully programmable
Free Quota and Framework Support
ClawEmail is currently in beta. Each account can create 5 agent mailboxes free with a 3,000-message monthly sending quota — enough to validate scenarios and run small-scale usage; beyond that, usage-based billing and paid upgrades will follow.
On the integration side, ClawEmail works with any framework that can receive HTTP requests, ships Python and Node.js SDKs, and publishes integration examples for mainstream frameworks including LangChain, Coze, and Dify. If your agent is already an API endpoint, a webhook receives the mail directly — no glue code.
Real Production Use Cases
Developers across several domains are already putting it to work:
- Tech team leads forward contracts, quotes, and invoices to the agent mailbox; the agent extracts key fields, structures them, and replies with a summary table
- DevOps engineers route Grafana and Sentry alerts to the mailbox, where the agent deduplicates, grades by severity, and compresses 200 daily alerts into 4 digest emails
- Independent consultants train an agent on their FAQ; prospective clients email questions and get instant answers to 80 percent of common ones — a 24/7 first-line assistant
- Indie developers wire a PDF-to-Word tool to a dedicated mailbox: users email a PDF and receive the converted document 30 seconds later
Versus Cloudflare Email Workers — and Why the Difference Matters
ClawEmail’s positioning resembles Cloudflare’s email AI-processing flows: both let AI interact with users through email. ClawEmail’s edge is infrastructure — it provides the complete mailbox layer on the @claw.163.com domain, where the DIY route requires you to own a domain and configure DNS yourself. That difference collapses the setup barrier from an afternoon of DNS archaeology to a single command.
For users of OpenClaw, Hermes, and similar agent platforms, ClawEmail effectively adds an email channel alongside the usual WeChat, Feishu, Slack, and Discord integrations — with one property none of those channels share: everyone on the internet already knows how to use it. Chat platforms require the counterparty to install something or join something. Email requires nothing.
Why Email Is the Right Interface — Again
There is a quiet insight underneath the product: every agent-interface generation so far has demanded something from the human on the other side. APIs demand an engineer. Chat platforms demand an account, an install, and often a mutual connection. Web portals demand a browser session. Email demands nothing except literacy in a protocol every internet user already operates daily. That is why the agent-identity trend matters beyond convenience. When an agent holds a real, addressable identity on the world’s oldest universal messaging network, it becomes callable by the least technical person you know — a client, a parent, a supplier — without onboarding of any kind. The mailbox stops being a place where agents get spam-filtered and becomes a place where they do work.
NetEase is one of the first major providers to ship that premise as a product, and the details show unusual care for the developer path: a real domain rather than a subaddress on your own inbox, an API and CLI alongside the mailbox, SDKs for the two ecosystems where agents actually live, and webhook delivery for agents that are already endpoints. The beta is free at claw.163.com for anyone curious enough to register.
The Bottom Line
ClawEmail is a small product with a large implication: agent interfaces are ripening from developer-only constructs (APIs, SDKs, webhooks) into the most universal interface humanity has. The three-step setup, the programmable mail-cli engine, and the practical use cases — alert triage, document extraction, FAQ screening, file conversion — show the pattern working today, not in a roadmap. If your agent can receive an email, it can receive work. The beta’s free tier makes that thesis easy to test this week.
