Identity Primitives

Agent email and inbox

Every new Iris identity receives an available managed @humiris.com address. Agents can send approved messages and read received email through the dashboard, CLI, REST API, or MCP. Users do not need to buy a domain, configure DNS, or connect an email provider.

Create an agent with an address

Terminal

iris agents create alex-sdr --first-name Alex --last-name Rivera --json

Managed by Iris Identity

Custom domains are optional. They are only needed when you want the sender to use your own brand domain.

Read the inbox

Terminal

iris inbox list AGENT_ID --unread --json
iris inbox read AGENT_ID MESSAGE_ID --json

Inbox results include the sender, subject, plain-text body, attachment metadata, unread state, and extracted HTTP(S) links. The dashboard highlights links that appear to confirm, verify, activate, approve, invite, or reset an account.

Email links are untrusted

Iris never opens a confirmation link automatically. An autonomous agent must show the sender, destination host, and intended effect and obtain approval before using a browser or another external tool to open it.

Send an approved message

Terminal

iris email send AGENT_ID \
  --to recipient@example.com \
  --subject "Approved subject" \
  --body "Approved body"

Direct API

Terminal

curl -X POST https://humiris.com/api/agents/AGENT_ID/email/send \
  -H "Authorization: Bearer $HUMIRIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to":"recipient@example.com","subject":"Approved subject","message":"Approved body"}'

Terminal

curl "https://humiris.com/api/agents/AGENT_ID/email/inbox?unread=true&limit=50" \
  -H "Authorization: Bearer $HUMIRIS_API_KEY"

Receiving is platform-managed

Inbound delivery requires Iris's receiving MX record and signed provider webhook. If the inbox reports that receiving is unavailable, the Iris team must repair the managed infrastructure; users should not configure Resend or DNS.

See the API reference for supported endpoints.