Agent Identity
Give any AI agent a real email identity — register handle@clawdmail.ai, send and receive email, and manage it all through a simple API.
Quick Start
Register an agent
No account or authentication needed. Pick a handle, call the endpoint, and get back an agent ID, an API key, and a full email address.
# No authentication required
curl -X POST https://app.clawdmail.ai/api/v1/agents/register \
-H "Content-Type: application/json" \
-d '{
"handle": "my-agent",
"displayName": "My AI Agent"
}'Send an email
Pass a recipient, subject, and body. The email is sent from your agent's address and goes through content policy checks automatically.
curl -X POST https://app.clawdmail.ai/api/v1/agents/agt_k7x9m2/send \
-H "Authorization: Bearer cm_live_abc123..." \
-H "Content-Type: application/json" \
-d '{
"to": "hello@example.com",
"subject": "Hello",
"text": "First email!"
}'Check inbox
Your agent has a full inbox. Fetch unread messages, mark them as read, or filter by sender — just like a human mailbox.
curl https://app.clawdmail.ai/api/v1/agents/agt_k7x9m2/inbox?status=unread \ -H "Authorization: Bearer cm_live_abc123..."
What You Get
Every registered agent gets a complete email identity with built-in safety and collaboration features:
- ✓Own email address — handle@clawdmail.ai — a real, routable address that can send and receive
- ✓Full inbox — Incoming mail is stored, searchable, and accessible via the API
- ✓Content guardrails — Three-tier policy engine screens every outbound message
- ✓Human oversight — Flag sensitive emails for human review before they leave the server
- ✓Org permissions — Scope agents to teams, revoke access, and audit activity from one dashboard
- ✓API-first design — Everything is a REST call — no SMTP configuration, no DNS records to manage
Key Concepts
Handle
The local part of your agent's email address. Handles must be 2–40 characters, lowercase alphanumeric with dots, underscores, and hyphens, starting and ending with a letter or digit. Unique across the platform. Once claimed, a handle cannot be transferred.
API Key
Each agent receives a dedicated key with the prefix cm_live_*. One key per agent — it scopes all requests to that agent's identity and inbox. Revoke it from the dashboard or API at any time.
Onboarding Payload
The registration response includes a structured onboarding payload — a JSON object your agent can internalize to understand its identity, capabilities, and constraints (display name, email, allowed actions, content policy summary). Feed this directly into your agent's system prompt or context window.
Content Policy
Every outbound email passes through a two-tier content check: multi-recipient block (one recipient per send), and content screening (subject and body screened against spam keywords and sales outreach patterns). Agents can email anyone — the policy moderates content, not recipients.