# Cyberpigeon > Azure-hosted email API and persistent mailboxes for AI agents. ## Availability Invite-only private beta. Mail delivery activation is in progress. Sending and receiving require provider and domain activation. Create a workspace to manage mailboxes. Business subscriptions use Stripe Checkout with automatic tax. Launch: USD 49/month for 100 mailboxes and 10,000 units. Scale: USD 149/month for 1,000 mailboxes and 50,000 units. Extra monthly blocks: USD 20 per 10,000 units. Prices exclude applicable tax. No automatic overages. Payment does not activate email delivery. Manage billing and cancellation at /console#billing. ## Product and documentation - [Cyberpigeon | Email API & Inboxes for AI Agents](https://cyberpigeon.ai/): Give AI agents email addresses, persistent inboxes and scoped API keys. Explore Cyberpigeon’s REST API, custom domains and private beta. - [Pricing & Plans for Agent Email | Cyberpigeon](https://cyberpigeon.ai/pricing): Compare Cyberpigeon’s free beta and Launch and Scale plans. Review mailbox limits, monthly email units, add-on capacity and activation requirements. - [Agent Inbox & API Key Management | Cyberpigeon](https://cyberpigeon.ai/guides/agent-email-console): Use the Cyberpigeon console to manage agent inboxes, inspect sent and received messages, scope API keys, export data and control account access. - [Why AI Agents Need Email | Cyberpigeon](https://cyberpigeon.ai/why-agents-need-email): Learn when AI agents need email for persistent identity, delayed replies and scoped access. Explore real workflows and when a direct API is a better fit. - [AI Agent Email Workflows & Use Cases | Cyberpigeon](https://cyberpigeon.ai/use-cases/agent-email-workflows): Practical email workflows for AI agents: collect supplier quotes, coordinate customer support, request documents, and follow up with human approval. - [Agent Email API Quickstart | Cyberpigeon](https://cyberpigeon.ai/guides/agent-email-api): Build with the Cyberpigeon REST API: provision an agent mailbox, authenticate with scoped keys, send idempotently, poll events, and reply to messages. - [Cyberpigeon vs AgentMail vs Resend: Email APIs](https://cyberpigeon.ai/compare/email-apis-for-agents): Compare agent inbox platforms and general email APIs. Review Cyberpigeon, AgentMail, and Resend by mailbox model, inbound events, integration, and availability. - [Custom Email Domains for AI Agents | Cyberpigeon](https://cyberpigeon.ai/guides/custom-email-domains): Connect your own email domain to Cyberpigeon. Verify ownership, configure sending and receiving DNS records, and create agent inboxes on your domain. - [Interactive API reference](https://cyberpigeon.ai/docs) - [OpenAPI specification](https://cyberpigeon.ai/openapi.json) ## Account and privacy controls The console supports email/password accounts, scoped API keys, cross-agent email logs, recovery codes, account data export and closure. Public registration requires confirmed operator/contact details; delivery requires provider activation and account approval. No GDPR certification is claimed. - [Privacy notice](https://cyberpigeon.ai/legal/privacy) - [Terms and acceptable use](https://cyberpigeon.ai/legal/terms) - [Cookies](https://cyberpigeon.ai/legal/cookies) - [Subprocessors](https://cyberpigeon.ai/legal/subprocessors) - [DPA preparation](https://cyberpigeon.ai/legal/dpa) ## Integration facts - Bearer account keys provision mailboxes and manage keys. Agent keys are scoped to a mailbox and read/send permissions. - POST /v1/mailboxes returns mailbox information and an initial agent key. - POST /v1/mailboxes/{mailboxId}/messages requires Idempotency-Key. HTTP 202 means queued, not delivered. - Poll GET /v1/events with a persisted after cursor. Customer-configurable push webhooks are not currently available. - Reply through POST /v1/mailboxes/{mailboxId}/messages/{messageId}/reply. - Cyberpigeon is not a Gmail/Outlook account provider, OAuth mailbox connector, SMTP/IMAP service, or autonomous agent runtime. - No published SDK package, MCP server, or outbound attachments yet. - Custom domains: account keys can add /v1/domains, prove DNS ownership, and check provider sending/receiving records. Pass domain_id when creating a mailbox after both directions are verified. Provider activation is required for mail DNS and delivery. - Workflow decisions, extraction, approval, and task state belong to the integrating application. Public documentation reviewed: 2026-09-11. This index helps tools navigate documentation; it is not a claim of search inclusion or ranking.