Email

Available now. Email ships with Identity, on Vetta’s own email layer, gated by the policy layer. Inbound mail is verified and stored; the wake is coming soon.

An identity can own one or more real inboxes. An inbox lives on a verified web domain, and its address is simply 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:

Action	Requires
Create an inbox	domain `status: active`
Send	domain `dns_status: provisioned`
Receive	domain verified for inbound at the email layer

At signup Vetta auto-provisions a system domain ({org-slug}.<vetta-apex>) that is already sending- and receiving-ready, so you can create an inbox immediately without touching a registrar.

Addresses: auto vs. manual localparts

Auto-provisioned
Manual

When Vetta 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.

agent "Ava Sales"  →  ava-sales@acme-mail.com
(collision)        →  ava-sales-2@acme-mail.com

When you choose the address, the localpart must match [a-z0-9._-] and be at least 2 characters.

CLI

vetta identity email provision --identity ava --address ava@acme-mail.com

Provision an inbox

Ensure a verified domain

CLI

vetta identity domain list        # need status: active (+ provisioned to send)

Create the inbox

vetta identity email provision --identity ava --address ava@acme-mail.com

const inbox = await vetta.emails.create(identity.id, {
  address: "ava@acme-mail.com",
});

curl https://api.vetta.sh/v1/identities/$IDN/emails \
  -H "Authorization: Bearer $VETTA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "address": "ava@acme-mail.com" }'

Send and receive

Sending is gated on domain verification and is credit-checked; inbound mail wakes the owning agent.

Sending mail

The agent sends through a send_email tool bound to the identity. Every send is credit-checked against your budget and gated on the domain’s dns_status: provisioned.

vetta identity email send --identity ava \
  --to customer@example.com \
  --subject "Your refund" \
  --text "We've processed your refund for order #4821."

// The inbox is addressed by id, not by its `from` address: one identity can hold several.
await vetta.emails.send(identity.id, inbox.id, {
  to: ["customer@example.com"],
  subject: "Your refund",
  text: "We've processed your refund for order #4821.",
});

A send issued before the domain finishes verifying returns a retryable job_not_ready rather than a hard error — the durable runtime can retry once the domain is provisioned.

Receiving mail

Inbound email flows through Vetta’s email layer and becomes an agent wake:

Arrive via webhook

The email layer delivers the message to Vetta’s inbound webhook.

Match to an inbox

Vetta matches the recipient to an active inbox by exact address. No match → the message is not routed.

Store and wake

The message is stored, and the owning agent’s alarm is set. A sleeping agent wakes through the durable runtime, reads the mail in one turn, acts, commits, and sleeps.

CLI

vetta identity email list --identity ava     # inboxes + recent messages

See Inbound for the full wake-handle-sleep path shared by email, SMS, and connection events.

Next: phone

Provision a number and send SMS over carrier-registered messaging.

Agent

Running an agent

Agent capabilities

Computer

Identity

Team

The domain comes first

Addresses: auto vs. manual localparts

Provision an inbox

Sending mail

Receiving mail

Next: phone

​The domain comes first

​Addresses: auto vs. manual localparts

​Provision an inbox

​Sending mail

​Receiving mail

Next: phone

The domain comes first

Addresses: auto vs. manual localparts

Provision an inbox

Sending mail

Receiving mail