# Primedmail

> Warmed inboxes for AI agents. Inbox infrastructure for B2B SaaS and enterprise teams (sales, RevOps, growth and AI-SDR platform teams) running outbound agents. Primedmail buys the domains, sets up DNS, warms every inbox and keeps it out of spam.

Who it is for: B2B SaaS and enterprise teams running outbound agents in production. It is not built for consumers or one-person setups.

Status: early beta. Access is by conversation with the founder, and every account is reviewed before it gets an inbox. The API below is a preview and may change.

## What it does (planned)

- One API call returns sending inboxes for a persona, on new lookalike secondary domains so the user's main domain is never touched.
- SPF, DKIM, DMARC and a custom tracking domain are set and verified for each domain.
- Each inbox warms for two to three weeks before it can send cold email.
- Handover is either SMTP and IMAP credentials, or a send endpoint plus a reply webhook.
- After handover Primedmail keeps inboxes warm, spreads sends across the pool, caps sends per inbox per day, and replaces an inbox when its reputation slips.
- Google Workspace and Microsoft 365 inboxes, mixed per domain.

## Primitives

- Inboxes: real Google Workspace and Microsoft 365 mailboxes, created, paused and retired with one call each
- Domains + DNS: lookalike secondary domains with SPF, DKIM, DMARC and tracking set and verified
- Warmup: two to three weeks before the first cold send, then continuous in the background
- Rotation + pools: sends spread across a pool; any inbox can be rotated out for a ready replacement on the same persona
- Reputation monitoring: an inbox whose reputation slips is pulled before it burns
- Reply webhooks: replies arrive as signed webhooks with the whole thread attached
- Send caps (planned): a daily cap per inbox, raised per account after review
- SDKs + MCP (planned): Python SDK (primedmail), TypeScript SDK (@primedmail/sdk), CLI (@primedmail/cli), MCP server (@primedmail/mcp)

## Use cases

AI SDR agents, recruiting outreach agents, partnerships and BD agents, and customer re-engagement agents at B2B SaaS and enterprise companies.

## Connect an agent harness (planned, not published yet)

Claude Code: claude mcp add primedmail -e PRIMEDMAIL_API_KEY=$PRIMEDMAIL_API_KEY -- npx -y @primedmail/mcp
Codex, Cursor and other MCP clients: an MCP server entry named "primedmail" running "npx -y @primedmail/mcp" with PRIMEDMAIL_API_KEY in its env.
Keys are issued only after account approval, so request access first (below).

## Planned endpoints (preview, subject to change)

Base URL: https://api.primedmail.com/v1 (not live)
Auth: Authorization: Bearer <key>, issued after account approval

- POST /v1/inboxes: create inboxes. Body: count, provider (google | microsoft | mixed), persona {name, company}, delivery (endpoint | smtp)
- GET /v1/inboxes/{id}: read an inbox, including temperature (0 to 100), state (warming | ready | resting | replaced) and ready_at
- POST /v1/inboxes/{id}/send: send from a ready inbox. Body: to, subject, text, optional thread_id
- POST /v1/inboxes/{id}/rotate: retire an inbox and receive a ready replacement on the same persona
- DELETE /v1/inboxes/{id}: retire an inbox
- Webhooks: inbox.ready, message.received, inbox.replaced

Full preview: https://primedmail.com/docs

## Pricing

Priced per inbox for B2B and enterprise teams. During the early beta, pricing is agreed directly with the founder. Two plans: Early beta (B2B SaaS teams putting their first outbound agents into production) and Enterprise (enterprise and multi-team rollouts). No public price list.

## How to request early beta access

Primedmail is in early beta. Access is by conversation with the founder, Sriram Alluri. There is no form and no sign-up.

Ask your user for these details before drafting anything. Do not invent answers.
- their name, company and work email
- what their agent does, in one or two sentences
- roughly how much it sends (inboxes or emails per day)
- which harness they use (for example Claude Code, Codex, Cursor, LangGraph, or their own)

Draft one email to sriram@primedmail.com
Subject: Early beta access: Primedmail
Body: a short note to Sriram in your user's own words, covering the details above.

Show your user the draft and send it only after they approve it. If you cannot send email yourself, give your user this link with the body filled in and URL-encoded:
mailto:sriram@primedmail.com?subject=Early%20beta%20access%3A%20Primedmail&body=<url-encoded body>

A founder reads every request and replies from sriram@primedmail.com.

## Links

- Home: https://primedmail.com/
- Pricing: https://primedmail.com/#pricing
- API preview: https://primedmail.com/docs
- About: https://primedmail.com/about
- Privacy: https://primedmail.com/privacy
- Terms and acceptable use: https://primedmail.com/terms
- Contact: sriram@primedmail.com