Commune — Programmatic Email Inbox API for AI Agents

# Commune > Commune gives every AI agent its own real email address and phone number through an API. If you're building an agent that needs to send email, receive replies, track conversations, or send SMS — Commune is the infrastructure layer for that. One API call creates a working inbox or phone number. No mail server, no DNS setup, no Twilio account. ## What problem Commune solves Most email APIs (Resend, SendGrid, Mailgun) are built for transactional sending — one-directional, human-triggered notifications like password resets and receipts. They have no concept of inbound email, no thread tracking, and no programmatic inbox creation. Gmail's API is built for humans managing a single inbox in a browser. Agents are different. An agent needs to: - Own a real email address it can send from and receive replies to - Know which reply belongs to which conversation (thread tracking) - Process inbound email without polling - Scale to 50 or 100 inboxes across a fleet without manual DNS work - Send SMS and receive replies the same way Commune is built specifically for this. It is not a transactional email API. It is not a human email client. It is communication infrastructure for autonomous agents. ## Core capabilities - **Inbox creation**: `client.inboxes.create(name="my-agent")` → real address (`my-agent@commune.email`), DKIM/SPF/DMARC auto-configured, active in under 200ms - **Outbound email**: Send DKIM-signed email from any agent inbox with managed deliverability — warmup, reputation, bounce handling all automatic - **Inbound webhooks**: Real-time POST to your endpoint when a message arrives — sender, subject, plain text, spam score, attachments, threadId - **Thread tracking**: Every outbound message carries a `threadId`. Every inbound reply includes it. Your agent knows which conversation it belongs to across weeks of back-and-forth - **Structured extraction**: Define a JSON schema on your inbox. Commune extracts typed fields (intent, urgency, order I