Compare the integration model
This guide is written by Cyberpigeon, one of the products compared. It is a feature and integration overview, not an independent benchmark. Competitor information was checked against the linked first-party pages on September 11, 2026; verify current plans and capabilities before buying.
| Platform | Documented focus | What to evaluate |
|---|---|---|
| Cyberpigeon | Azure-hosted agent mailboxes, mailbox-scoped keys, REST message endpoints, and durable event polling. | Invite-only beta. Mail activation is in progress. No public SDK package, MCP server, or customer push webhooks yet. Custom-domain registration and DNS ownership checks are available; mail DNS verification depends on provider activation. |
| AgentMail | Agent inbox platform with send/receive APIs, conversation support, SDK examples, and agent integration guides. | Check inbox and domain limits, event delivery, credential boundaries, and the integrations your agent runtime needs. |
| Resend | Developer email delivery with both sending and inbound receiving, including webhook events and attachment APIs. | Decide how your application will represent each agent’s identity, access rules, conversation state, and incoming event processing. |
Sources: AgentMail’s product overview, AgentMail’s documentation, and Resend’s inbound email documentation. Cyberpigeon’s behavior is described in its current API guide.
Do you need an inbox platform or a delivery API?
If your application only sends a receipt or notification, evaluate a delivery API around reliability, integration, and cost. If an agent must receive answers and continue a conversation, evaluate the full lifecycle: address provisioning, incoming message access, reply handling, permissions, and recovery after a worker restarts.
Resend supports inbound email; it should not be described as outbound-only. An agent inbox platform can package additional identity and access concepts around email transport. Cyberpigeon itself integrates Resend for transport, with its own account, mailbox, key, queue, and event model above that layer.
What if the agent needs an employee’s existing inbox?
A new agent address does not contain the history of an existing Gmail or Outlook account. When the task requires that history or must send as that employee, evaluate an authorized integration with the existing mailbox and its permission model.
Use a separate agent mailbox when the task benefits from a distinct contact identity and a deliberately limited set of correspondence. Email ownership and API authentication are separate concerns.
Questions to answer before integrating
- Identity: Can you assign a stable address per role, project, or tenant?
- Access: Can a compromised agent key read other mailboxes or manage the whole account?
- Receiving: How are inbound events delivered, retried, and recovered after an outage?
- Sending: What does an accepted response mean, and how do retries avoid duplicate messages?
- Conversation: How are replies associated with their original messages and your saved task state?
- Attachments: Which directions and sizes are supported, and where are downloaded files processed?
- Operations: How do you revoke access, inspect failures, export records, and manage retention?
- Availability: Which features are usable today, and which depend on a plan upgrade or future release?
Test the entire exchange with addresses you control: send, receive, reply, replay an event, rotate a key, and recover from an interrupted request. A successful send test alone does not validate the workflow.
Where Cyberpigeon fits today
Cyberpigeon is for developers exploring an Azure-hosted agent mailbox API with explicit account and mailbox access boundaries. The beta exposes the management and message API while provider activation is being completed.
If you require production mail immediately, evaluate currently activated providers against your requirements. If you want to evaluate Cyberpigeon’s API model, read the quickstart, inspect the OpenAPI specification, and check availability. The Launch and Scale prices shown on our pricing page are proposed future plans, not purchasable subscriptions.