Available now. Email ships with Identity, on Naive Managed Agents’ own email layer, gated by the policy layer. Inbound mail is verified, stored and wakes the inbox’s agent.
localpart@domain — e.g. ava@acme-mail.com. Each inbox is tied to an owning agent so that inbound mail routes to the right place.
The domain comes first
Inboxes cannot exist on an unverified domain. The rules come straight from the domain readiness gate:Addresses: auto vs. manual localparts
- Auto-provisioned
- Manual
When Managed Agents provisions an inbox for an agent, the localpart is derived from the agent name: slugified, truncated to ≤ 32 chars, and given a collision suffix if the address is already taken.
Provision an inbox
1
Ensure a verified domain
CLI
2
Create the inbox
3
Send and receive
Sending is gated on domain verification and is credit-checked; inbound mail wakes the owning agent.
Sending mail
The agent reads its inboxes withemail.inboxes / email.read and sends through email.send, tools bound to the session’s identity; email.send asks for approval by default. Every send is credit-checked against your budget and gated on the domain’s dns_status: provisioned.
Receiving mail
Inbound email flows through Managed Agents’ email layer and becomes an agent wake:1
Arrive via webhook
The email layer delivers the message to Managed Agents’ inbound webhook.
2
Match to an inbox
Managed Agents matches the recipient to an active inbox by exact address. No match → the message is not routed.
3
Store and wake
The message is stored and, unless a guard holds it, starts a session for the inbox’s owning agent as this persona (the agent must hold it). The agent reads the mail, may answer with
email.send from this inbox, commits, and sleeps.CLI
Next: phone
Provision a number and send SMS over carrier-registered messaging.