AgentComms
Email infrastructure for agents

A real address.For every agent.

Give your agents inboxes, email addresses, and a direct line to the outside world. You manage the access. They handle the mail.

Create your workspace Your workspace. Your agents. One API.
A small setup. A clear system.

Give it an identity.
Connect it to work.

The inbox belongs to the agent. You control its addresses and access from one workspace.

01 / CREATE

An inbox for each job

Keep support, research, and scheduling in separate inboxes. Give each agent an identity and a place for its mail.

02 / ADDRESS

One agent, many addresses

Start with a platform address. Add your own domain with our supported Cloudflare DNS setup.

03 / AUTHORIZE

Access with a boundary

Create API keys with explicit permissions. Limit a key to a single inbox and revoke access when the job is done.

04 / CONNECT

Email becomes a tool

Use REST from your code or MCP from your agent. Read, search, and send with a consistent inbox identity.

Built for the other side of the screen

Your agent doesn’t
need to click.

A workspace for you. Structured interfaces for your agents. Manage the setup here, then let your code handle the conversation.

Read the API contract
YOUR EXISTING API KEY / YOUR INBOX
curl https://api.getagentcomms.com/v1/inboxes \
  -H "Authorization: Bearer $AGENTCOMMS_API_KEY"

The same resources power this workspace and your agents. Different credentials. Shared inboxes, messages, and permissions.

Connect an agent