Welcome
Email and voice for your agent. Connect an email address and a phone number.
AgentOwl gives your agent an address in the real world. The Free path receives email in a hosted Inbox without a webhook. You can also connect your runtime for new messages in a shared JSON envelope. Outbound sending currently requires reviewed pilot setup; its 10-recipient daily limit applies once enabled. AgentOwl also gives your agent a phone number and connects incoming calls to your phone system or voice agent. SMS and AgentOwl-hosted conversation have separate availability.
Choose your next step
| Goal | Start here | Expected result |
|---|---|---|
| Receive incoming calls | Voice setup | Incoming calls connected to your voice system |
| Receive your first email | Quickstart | A message in your hosted Inbox |
| Connect your application | Run a durable receiver | One saved job and example worker output |
| Understand failure recovery | See delivery fail and recover | Retryable failure, acceptance, and intentional replay |
| Track optional agent work | From delivery to agent outcome | Clear runtime boundaries and opt-in setup |
Email setup starts with a workspace address. Sending requires separate review and enablement after the Inbox is active. Voice is available on Pro; contact support to connect a number to your phone system or voice agent. The account purchase review reports self-service availability. SMS and direct audio streaming remain separate preview paths.
Key concepts
- Workspace (a tenant in the API and CLI) — your isolated account space. Everything below belongs to one workspace.
- Binding — an email address or phone number attached to your workspace.
- Endpoint — where new events are delivered after you connect a runtime. An endpoint is optional for the Free hosted email Inbox.
- Route — connects a binding to an endpoint.
- Policy — a rule checked when a message arrives, such as blocking a sender.
- Activate routing (
config publish) — makes runtime delivery configuration live. The guided Free email Inbox can receive without a runtime route.
Channels
- Email —
<name>@<workspace>.agentowl.devaddresses with SPF, DKIM, and DMARC results - Text messages — later Pro setup for SMS and MMS
- Voice — a phone number and incoming calls for your agent; routing choices are in the voice guide
Reference
- Event format — the JSON every channel shares, headers, retries, and replay
- CLI Reference — every
agentowlcommand - Roles and Permissions — accounts, API keys, plan limits, and the audit log
Running AgentOwl yourself? See Self-hosting.