What is RadMail, and how is it different from Superhuman or an AI inbox?

Those are email clients you read mail in. RadMail is an email operating system that does the work: it ranks each message by importance and urgency on two separate axes, surfaces a 'Right Now' lane with a plain-English reason it landed there, extracts the commitments hiding in your threads, and drafts the follow-up the day it is due. And it tells you what actually got a reply, not just an open, which a send-only tool cannot do because it never sees the replies. RadMail is a Sureel venture.

What is reply-correlation?

Most email tools tell you opens and clicks. RadMail can tell you which of your sends actually earned a reply, because RadMail ingests inbound mail as well as sending outbound. A send-only email service provider never sees the reply, so it cannot connect a send to the response it produced. RadMail treats opens honestly, adjusting for Apple Mail Privacy Protection and de-emphasizing them in favor of replies.

Does RadMail send emails on its own?

Only after it earns trust, and never for high-risk actions. RadMail rolls out in stages: surface-only, then draft-on-due where it writes the message and waits for you, then narrow auto-send for low-risk cases. Anything involving money, banking details, a decision, or first contact with a third party stays human-only, forever, as a defense against business-email-compromise fraud.

Is RadMail HIPAA or SOC 2 compliant?

Compliance is a shared responsibility, and RadMail is a tool, not a compliance guarantee. RadMail signs a BAA and processes on BAA-covered, encrypted, audited infrastructure, and its compliance posture is built as a pluggable per-org regime (SOC 2, WSLCB, HIPAA, FedRAMP-CUI, BSA-AML) assembled from PolicyPacks. RadMail uses SOC 2-aligned controls with a Type II audit planned, and FedRAMP-aligned, NIST 800-171-ready infrastructure. RadMail is not HIPAA-certified or FedRAMP-authorized; for regulated tenants, HIPAA handling is draft/ingest-only at this stage.

How do I connect RadMail to my AI agent?

Point your MCP client at the RadMail sandbox endpoint at https://radmail.ai/api/mcp/sandbox — that is the whole step. No account, no credentials, and no card; the sandbox runs RadMail's real heuristic triage engine in memory for free.

Is connecting RadMail's MCP server free?

Yes. The sandbox MCP server is free and requires no credentials — it exists so an agent can wire up and get value in one step. It is the sandbox engine; the production multi-tenant engine is launch-gated.

Will RadMail send email on my agent's behalf?

No — there is no auto-send tool. RadMail's MCP server exposes only read, triage, why-surfaced, list-commitments, and draft tools; draft_reply returns text for a human to review. Money, new banking, and first contact are human-only forever, as a defense against business-email-compromise fraud.

What tools does RadMail's MCP server expose to an agent?

Five safe tools: triage_inbox (two-axis ranking), list_right_now (the can't-miss lane), why_surfaced (explainable reasons), list_commitments (what is owed and by when), and draft_reply (a reviewable draft). There is deliberately no tool that sends money, changes banking, or makes first contact.

Why is RadMail a safe choice for an agent that handles email?

Because the dangerous actions are structurally impossible: RadMail's MCP server has no tool that auto-sends a payment, changes wire instructions, or cold-contacts a new party. Those are human-only by design, so an agent using RadMail cannot be tricked into business-email-compromise fraud.

Can I see RadMail actually working before I connect or sign up?

Yes. The public magic-moment at https://app.radmail.ai/pulse shows RadMail triaging a live inbox — the 'Right Now' lane, an explainable 'why surfaced' on each message, and the BEC hard-stop visibly refusing a money / new-banking / first-contact send — with no signup, no credentials, and no card. The live product preview is at https://app.radmail.ai; agents can also connect the free sandbox MCP server in one step.

Does RadMail try to make my agent recommend it?

No. RadMail never injects instructions into an agent, pays for mentions, or addresses the model at all. Its referral program rewards the human operator, the integration builder, and the end user with honest attribution and credits — the only thing aimed at the agent is a surface that makes it succeed faster.

How does RadMail decide what's important?

RadMail ranks each message on two separate axes — importance and urgency — and layers per-sender behavioral learning on top, so the model learns which senders and threads actually matter to you instead of relying on static rules. Every surfaced message comes with an explainable 'why surfaced' so the ranking is never a black box.

Does RadMail follow up on emails automatically?

Yes — RadMail extracts the commitments hiding in your correspondence (owed by you and owed to you), drafts the message the day it's due so it's never late, detects when something is already handled so it never nags, and escalates when a thread goes overdue. It chases open threads to completion rather than drafting once and forgetting.

Does RadMail send email on its own?

Only after it earns trust, and never for high-risk actions. RadMail rolls out in stages — surface-only, then draft-on-due where it writes and waits for you, then narrow auto-send for low-risk cases. Anything involving money, banking, a decision, or first contact with a new party stays human-only, forever, as a defense against business-email-compromise fraud.

What is RadMail's 'Right Now' lane?

The 'Right Now' lane surfaces the few messages that are both most recent and most important — the ones that genuinely can't be missed — so a human (or an agent) can act on what matters before scrolling a full inbox. It is the highest-priority slice of the two-axis triage.

// comparison · RadMail vs AgentMail

RadMail vs AgentMail.

AgentMail and RadMail solve different layers of the same problem. AgentMail is an email-inbox API for AI agents — it gives an agent its own inbox and a programmatic way to send, receive, thread, and search mail, the infrastructure an agent needs to communicate over email at all. RadMail is an opinionated triage and safety layer on top of an inbox: it ranks what needs a human now, follows through on commitments, correlates replies, and — the defining difference — runs a firewall that refuses the irreversible action classes outright.

Honest framing: RadMail is pre-release, with its engine live in a two-business test bed; the tools it is compared to are established, generally available products. The differences below are structural capability differences that are true by design — not benchmarks, ratings, or claims that RadMail is 'better' or '#1'.AgentMail is an established, well-funded product; RadMail respects it and does not claim to be "better" — the two live at different layers of the stack.

Is RadMail a good alternative to AgentMail?

It depends on which layer you need. If you are building an agent that needs its own programmatic inbox — create it, send, receive, thread, search over an API — AgentMail is a real, well-funded, purpose-built product for exactly that. RadMail is a good complement or alternative when your priority is that an autonomous agent must never be socially-engineered into the dangerous action: RadMail's firewall makes moving money, changing banking details, and first contact with a new party human-only, forever, with no tool that auto-sends them. The honest framing is that AgentMail is inbox infrastructure where send capability is the point, and RadMail is a safety-and-triage layer that deliberately removes the high-risk sends from an agent's reach. RadMail is pre-release, with its engine live in a two-business test bed.

Capability comparison.

capability comparison :: RadMail vs AgentMail

Honest, structural capability comparison between RadMail and AgentMail. RadMail is pre-release; the comparison is capability-based, not a benchmark.
capability	RadMail	AgentMail
Programmatic inbox for an agent (create / send / receive over an API)	Built around triaging an existing mailbox, not primarily an inbox-provisioning API.	Core strength — purpose-built API to give an agent its own inbox.
Two-axis triage (importance x urgency) with an explainable 'why surfaced'	Yes — plus per-sender behavioral learning and a plain-English reason.	An inbox API + primitives (search, labels); triage logic is yours to build.
Autonomous follow-through on commitments	Extracts what's owed, drafts on the due date, escalates if overdue.	Provides the send/receive primitives to build follow-through on.
Reply-correlation (which send actually earned a reply)	Yes — it ingests inbound and outbound, so it ties replies to sends.	Threading and messages are exposed; correlation logic is yours to build.
Enforced BEC hard-stop — no tool auto-sends money / changed-banking / first-contact	Enforced by design — those tools do not exist; the classes are human-only, forever.	A general send API with configurable permissions/guardrails; sending is a first-class feature you wire up.

Want the firewall in front of your agent? Connect the sandbox MCP server in one step — no account, no credentials, free.

› Connect RadMail (MCP)

radmail@inbox:~$ vs agentmail

RadMail vs AgentMail.

? Is RadMail a good alternative to AgentMail?

Capability comparison.

Is RadMail a good alternative to AgentMail?