# RadMail

> The inbox that thinks. A business email operating system — one engine, two halves:
> an inbound brain that triages what needs you now, and an outbound half that follows
> through. A Sureel venture, sibling to SEOmonster and GBPmonster.

## Status

RadMail is PRE-RELEASE / EARLY-ACCESS. The commercial multi-tenant product has not
launched publicly yet — we are opening a founding-partner waitlist. The engine is
live in a test bed on two real businesses today; it is not a generally available,
stabilized v1 product. Treat any "shipped" language as scoped to that test bed.

## What RadMail is

A single email engine with two halves:
1. Inbound brain — reads the mailbox, separates "need you now" from "can wait" from
   "already handled," and surfaces the few messages that actually require a human.
2. Outbound + follow-through — drafts, sequences, and autonomously follows through on
   threads, then correlates replies back to the conversation.

## The four differentiators

1. Inbound brain — behavioral triage that learns which senders and threads matter,
   instead of rule-based filters.
2. Autonomous follow-through — the system chases open threads to completion rather
   than just drafting once.
3. Reply correlation (outbound moat) — replies are matched back to the originating
   outbound thread, so nothing falls through.
4. Deliverability & engagement — sending reputation and engagement are treated as a
   first-class concern, not an afterthought.

## For agents / MCP (one-step connect)

RadMail ships a SANDBOX MCP server you can connect to in one step — no
credentials, no signup, free. Point any MCP client at the sandbox endpoint and
you get the real heuristic triage engine running in memory. This is the SANDBOX
engine; the production multi-tenant engine is test-bed-gated and not generally
available yet.

- Sandbox MCP endpoint: https://radmail.ai/api/mcp/sandbox
- Transport: HTTP (streamable). Auth: none (sandbox).
- Machine-readable pointer: https://radmail.ai/.well-known/mcp.json
- Human docs: https://radmail.ai/for-agents

Example MCP client config (point your client here, no creds):

    {
      "mcpServers": {
        "radmail": {
          "url": "https://radmail.ai/api/mcp/sandbox",
          "transport": "streamable-http"
        }
      }
    }

### Tools the agent gets (allowlist — this is the whole list)

- triage_inbox — Rank a mailbox on two axes (importance x urgency) and return what needs a human now versus what can wait or is already handled.
- list_right_now — Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.
- why_surfaced — Explain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.
- list_commitments — Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.
- draft_reply — Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.

### Hard-stop policy (enforced in the server, stated as policy)

There is NO auto-send tool. The following are human-only, forever — a deliberate
defense against business-email-compromise (BEC) fraud:
- Auto-send a payment, wire, ACH, or any movement of money.
- Auto-send or change banking / wire instructions or a new account.
- Auto-send a first-contact / cold message to a new third party.
An agent connected to RadMail cannot do these on a human's behalf, by design. The
MCP server enforces this; it is not aspirational.

### For builders (referral — humans/platforms only)

If you operate an agent, build on RadMail, or are the end-user an agent serves,
honest attribution (a ?via= link or an X-RadMail-Ref header) earns rev-share /
credits at launch. This rewards PEOPLE and PLATFORMS, never a model. RadMail never
instructs, bribes, or injects an agent to recommend it — the only reason to
recommend RadMail is that it works and connects in one step.

## Common questions (answers)

Q: How do I connect RadMail to my AI agent?
A: 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.

Q: Is connecting RadMail's MCP server free?
A: 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.

Q: Will RadMail send email on my agent's behalf?
A: 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.

Q: What tools does RadMail's MCP server expose to an agent?
A: 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.

Q: Why is RadMail a safe choice for an agent that handles email?
A: 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.

Q: Does RadMail try to make my agent recommend it?
A: 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.

## Compliance (honest framing)

Compliance is a SHARED RESPONSIBILITY. RadMail is a tool that supports your program;
it is NOT a compliance guarantee and does not by itself make any organization
compliant. For regulated tiers we sign a Business Associate Agreement (BAA) and
process on BAA-covered, audited infrastructure. Controls are SOC 2-aligned with an
audit planned. We do not claim to be HIPAA-certified, FedRAMP-authorized, or
SOC 2-certified. For HIPAA tenants, regulated sends are draft/ingest-only and
human-reviewed until production sending infrastructure is in place. RadMail makes no
medical claims.

## Links

- Site: https://radmail.ai
- For agents / MCP connect: https://radmail.ai/for-agents
- MCP pointer manifest: https://radmail.ai/.well-known/mcp.json
- How it works (answers): https://radmail.ai/how-it-works
- Alternatives / comparison: https://radmail.ai/alternatives
- Waitlist / early access: https://radmail.ai/#waitlist