Coming soon · Not affiliated with Nous Research

Turn every email into a controlled agent workflow.

HermesAgentMail gives Hermes agents real email addresses, then routes every message through approvals, memory, tasks, MCP tools, and audit logs. Your agents can read, draft, escalate, and reply — without losing human control.

Root-domain agent addressesHuman approval before sendHermes-native routingMCP-controlled toolsQueue-first processingAgora visibility
support@hermesagentmail.comSupport Agent · approval required
Awaiting approval
Pricing for 20 agent inboxes2m ago

from client@example.com

Classified: pricing questionFirst-time senderTask created
Received
Classified
Routed
Drafted
Awaiting approval
Sent

Approval required

Reason: first-time external sender

Policy: Support Agent cannot auto-send to new contacts

POST /events/inbound
workflow.json
{
  "type": "workflow.email.received",
  "message_id": "msg_123",
  "workflow_id": "wf_support",
  "to": "support@hermesagentmail.com",
  "classification": "pricing_question",
  "routed_to": "support-agent",
  "approval_required": true,
  "status": "queued"
}
Agora event stream
  • 10:02Routed to Support Agent
  • 10:03Pricing memory searched
  • 10:04Draft created
  • 10:05Human approval requested
Reply sent after approval
Delivered
Audit logged · every step traceable
Coming soon

Get early access to HermesAgentMail.

Join the waitlist and we'll email you the moment agent email workflows go live.

Beyond the inbox

Agent inboxes are only the beginning.

An inbox gets the email into your system. HermesAgentMail handles what happens next: routing, permissions, memory lookup, task creation, approval, sending, and auditability.

Not just an inbox

Every address is connected to an agent, workspace, policy, memory namespace, task flow, and approval rule.

Not uncontrolled automation

Agents can draft, classify, and escalate by default. Sending externally can require human approval, trusted sender rules, and volume limits.

Not hidden agent behavior

Every read, draft, approval, send, webhook, and task action is logged so operators can see exactly what happened.

The problem

Agents need more than inboxes.

Giving an AI agent an email address is easy. Trusting it with customer communication is harder. HermesAgentMail adds the missing operations layer: routing, permissions, approvals, memory, task creation, and visibility.

Inbox APIs stop too early

Most email APIs deliver the message. HermesAgentMail helps decide what the agent should do next.

Autonomous replies create risk

Agents need policy boundaries: who they can reply to, when approval is required, what attachments are allowed, and how much they can send.

Teams need visibility

Operators need to see pending approvals, agent decisions, created tasks, failed sends, and audit logs in one place.

How it works

From inbound email to approved action.

A predictable pipeline turns raw inbound email into controlled, auditable agent actions.

01

Claim an agent address

Spin up an address like support@hermesagentmail.com and connect it to an agent workflow.

02

Receive safely

HermesAgentMail receives the email, verifies the event, stores metadata, deduplicates it, and queues the work.

03

Classify and route

The message is routed by workspace, address, sender, policy, and agent role.

04

Search memory and context

The agent can use approved MCP tools to retrieve thread history, workspace context, or Hermes memory.

05

Draft, task, or escalate

The agent drafts a reply, creates a task, asks another agent, or escalates to a human.

06

Approve and send

Policy decides whether the reply can be sent automatically or must wait for human approval.

07

Update Agora and audit logs

Every workflow step becomes visible in Agora and auditable in the log.

Workflow engine

The workflow layer your agents need.

HermesAgentMail turns raw email into structured work.

Intent classification

Detect support requests, sales leads, invoices, bug reports, scheduling requests, newsletters, and urgent issues.

Agent routing

Route messages to the right Hermes agent based on address, sender, workspace, keywords, or policy.

Memory lookup

Let agents retrieve approved context before drafting a reply.

Task creation

Turn important emails into follow-up tasks, finance tasks, support tasks, or engineering tasks.

Approval policies

Require human approval for first-time senders, risky topics, external recipients, attachments, or high-value actions.

Agent collaboration

Allow one agent to ask another agent for help before a reply is sent.

Agora visibility

Show email events, agent decisions, tasks, and approvals inside the Hermes Agora workspace.

Audit trail

Record what was received, who or what handled it, what was drafted, who approved it, and when it was sent.

Features

Everything agents need to handle email safely.

Programmable primitives for routing, approving, tasking, and sending — built for controlled agent workflows, not human inbox clutter.

Controlled agent addresses

Claim addresses like support@hermesagentmail.com, luke@hermesagentmail.com, or finance@hermesagentmail.com and connect each one to an agent workflow.

Human approval by default

Agents can draft and prepare replies while humans stay in control of what leaves the workspace.

Policy-based sending

Control who agents can email, when they need approval, how often they can send, and whether attachments are allowed.

Email-to-task workflows

Convert inbound messages into support tickets, finance reviews, sales follow-ups, research summaries, or engineering tasks.

Hermes-native routing

Wake the right Hermes agent from inbound email and route the message with structured context.

MCP-controlled tools

Expose safe tools like get_email, search_thread, draft_reply, request_approval, send_reply, create_task_from_email, and update_agora.

Queue-first reliability

Accept inbound events quickly, queue work safely, and process asynchronously with rate limits.

Workspace isolation

Keep each customer, workspace, agent, address, API key, and message scoped correctly.

Audit logs

Track message reads, drafts, approvals, sends, rejected actions, webhook events, and API usage.

Delivery tracking

Monitor queued, sent, delivered, bounced, failed, complained, and suppressed messages.

Secure attachments

Control attachment download, storage, scanning, size limits, and agent permissions.

Usage and abuse limits

Protect customers and the platform with inbound, outbound, per-agent, and per-workspace limits.

Architecture

Built for bursty email and controlled agent action.

HermesAgentMail does not process AI replies inside the inbound webhook. The webhook is only the front door. It verifies the provider event, stores metadata, checks idempotency, enqueues work, and returns quickly. Workers handle retrieval, storage, routing, agent execution, approvals, and outbound delivery.

Email received
Verified webhook
Idempotency check
Durable queue
Worker processing
Message storage
Intent classification
Agent router
Memory / context lookup
Draft or task
Policy engine
Human approval
Outbound queue
Send provider
Delivery event
Agora update
Audit log
Policy engine

Agent autonomy with boundaries.

Give agents the ability to work without giving them unlimited permission to send.

Support Agent
support@hermesagentmail.com
  • Can read inbound support email
  • Can draft replies
  • Requires approval for first-time senders
  • Cannot send attachments
  • Max 50 outbound emails/day
  • Auto-reply allowed only for trusted domains
Finance Agent
finance@hermesagentmail.com
  • Can receive invoices
  • Can extract invoice details
  • Can create approval tasks
  • Cannot send payment instructions
  • All outbound replies require approval
Research Agent
research@hermesagentmail.com
  • Can receive newsletters and reports
  • Can summarize and store memory
  • Can create research notes
  • Cannot send external replies automatically
Sales Agent
sales@hermesagentmail.com
  • Can qualify inbound leads
  • Can draft follow-ups
  • Requires approval for pricing promises
  • Auto-reply disabled for new domains

MCP-ready for agent runtimes.

Agents do not get raw SMTP credentials or unrestricted inbox access. They call controlled tools. HermesAgentMail enforces workspace boundaries, policies, approvals, usage limits, and audit logs.

get_email(message_id)search_thread(thread_id)search_memory(query)classify_email(message_id)draft_reply(message_id)request_human_approval(draft_id)send_approved_reply(approval_id)create_task_from_email(message_id)assign_to_agent(message_id, agent_id)mark_handled(message_id)update_agora(event)get_agent_policy(agent_id)check_send_permission(agent_id, recipient)

Built around Hermes workflows.

HermesAgentMail is designed for Hermes agents, not just generic automation. An email can wake the right agent, provide structured context, search memory, create a task, request approval, and update Agora when the workflow changes.

  1. 1Email to support@hermesagentmail.com
  2. 2HermesAgentMail receives and queues
  3. 3Policy selects Support Agent
  4. 4Agent searches memory
  5. 5Agent drafts reply
  6. 6Task created
  7. 7Human approves
  8. 8Reply sent
  9. 9Agora event updated
  10. 10Audit log written
Agora visibility

See agent email work as it happens.

In Hermes Agora, emails can become visible workflow events. Watch messages arrive, agents process them, tasks appear, approvals wait, and replies go out — without hiding agent behavior in a black box.

  1. 10:02
    Email received
  2. 10:02
    Routed to Support Agent
  3. 10:03
    Pricing memory searched
  4. 10:04
    Draft created
  5. 10:05
    Human approval requested
  6. 10:08
    Reply approved
  7. 10:08
    Reply sent
  8. 10:09
    Agora updated
Agent activeAwaiting approvalTask createdReply sentAudit complete
Trust

Trust controls from day one.

HermesAgentMail is an email processor for agent workflows. Customers trust the platform to receive, route, and store email for their agents. We design around transparency, access controls, auditability, and clear permissions.

Workspace isolation
Encryption in transit and at rest
Webhook signature verification
API keys with scoped permissions
Human approval mode
Rate limits and abuse prevention
Audit logs
Reserved system addresses
Bounce and complaint tracking
Data deletion / export controls
Use cases

Agent email workflows for real teams.

Claim root-domain addresses and point them at the agent workflow that should handle the work.

Customer support workflow

support@hermesagentmail.com

Classify customer questions, draft replies, create support tasks, and require approval for sensitive answers.

Founder operator workflow

luke@hermesagentmail.com

Let an operator agent triage requests, summarize threads, create tasks, and prepare replies for approval.

Finance workflow

finance@hermesagentmail.com

Receive invoices and receipts, extract details, create approval tasks, and prevent unauthorized payment replies.

Research workflow

research@hermesagentmail.com

Collect newsletters, reports, documents, and requests, then summarize them into searchable memory.

Sales workflow

sales@hermesagentmail.com

Handle inbound leads, qualify requests, draft follow-ups, and require approval before pricing commitments.

Engineering workflow

dev@hermesagentmail.com

Turn monitoring alerts, GitHub notifications, bug reports, and customer issues into engineering tasks.

Developers

Developer primitives for controlled agent workflows.

Create workflows, receive verified workflow events, request approvals, and send approved replies through a controlled API — no mail server to run.

Create a workflow
request
POST /api/workflows

{
  "address": "support",
  "agent": "support-agent",
  "approval_required": true,
  "memory_namespace": "support",
  "create_tasks": true,
  "auto_reply": false,
  "trusted_senders": ["@customer.com"]
}
Response
response.json
{
  "email": "support@hermesagentmail.com",
  "workflow": "support-agent-email",
  "status": "active",
  "approval_mode": "required"
}
Approve and send a drafted reply
approve
POST /api/approvals/app_123/approve

{
  "edited_body": "Thanks for reaching out. For 20 agent inboxes...",
  "send_now": true
}
Pricing

Start small. Scale safely.

Transparent plans with usage limits that protect deliverability, security, and your costs.

Free
$0/mo
Test one controlled agent workflow.
  • 1 agent workflow
  • 25 inbound emails / month
  • 10 outbound emails / month
  • Human approval required
  • Community support
Starter
$9/mo
Launch your first real support, research, or operator workflow.
  • 5 agent workflows
  • 1,000 inbound emails / month
  • 250 outbound emails / month
  • Webhooks
  • Basic audit logs
  • Human approval controls
Pro
Popular
$29/mo
Add MCP tools, approval policies, routing, and email search for multiple agents.
  • 25 agent workflows
  • 10,000 inbound emails / month
  • 2,500 outbound emails / month
  • MCP tools
  • Advanced routing
  • Approval policies
  • Email search
Business
$99/mo
Run team-level agent email operations with advanced audit logs and higher usage limits.
  • 100 agent workflows
  • 50,000 inbound emails / month
  • 10,000 outbound emails / month
  • Team workspaces
  • Advanced audit logs
  • Priority support
Enterprise
Custom
Dedicated capacity, custom controls, security review, and deeper Hermes integration.
  • Custom volume
  • Custom limits
  • Dedicated worker capacity
  • Security review
  • Deeper Hermes integration

Inbound and outbound emails both count toward monthly usage.

FAQ

Questions, answered honestly.

What HermesAgentMail is, what it is not, and how it protects your data.

Coming soon

Be first to give your agents controlled email.

HermesAgentMail is not open to the public yet. Join the waitlist and we'll email you when workflows, approvals, and Agora visibility go live.

No spam. Just a single launch notification.

Give your agents email — and keep control.

Create root-domain agent addresses, route inbound messages into Hermes workflows, require approvals, create tasks, and make every action visible.