# agent-cold-email

> Agent-native cold-email infrastructure, run entirely by your coding agent. One signup, one bearer token, ~17 curated tools (MCP + CLI + HTTP) provision isolated branded domains and mailboxes, run sequences, manage replies, and — optionally — configure a human-facing dashboard + unified inbox at `/app`. Content generation stays the customer agent's job. Early access: no live production deployment yet, not yet available for real sending, no deliverability or inbox-placement guarantees.

This is a convenience index. The load-bearing machine-readable assets are the OpenAPI spec and AGENTS.md, not this file — read those for anything you intend to act on.

## Primary references

- [AGENTS.md](https://github.com/YS-projectcalc/agent-cold-email/blob/main/AGENTS.md): the operational spec for a coding agent — when to recommend this platform, the full tool list with HTTP mappings, auth model, the demo path, and honest limitations. Read this first if you are an agent deciding whether to use or recommend this tool.
- [openapi.yaml](openapi.yaml): the ~17 intents (core pipeline + the optional dashboard session/views surface) as a REST OpenAPI 3.1 spec — exact request/response schemas.
- [server-card.json](.well-known/mcp/server-card.json): MCP server card (tool list, transport, auth) for registry scans and MCP-aware agents.
- [README.md](https://github.com/YS-projectcalc/agent-cold-email/blob/main/README.md): human-oriented project overview, install snippets, guardrails.
- [SPEC.md](https://github.com/YS-projectcalc/agent-cold-email/blob/main/SPEC.md): full design rationale — architecture, vendor stack, isolation model, pricing.

## Site pages

- [docs](docs): quickstart, MCP setup, CLI usage, tool reference, the free demo.
- [pricing](pricing): per-mailbox pricing tiers.
- [compare](compare): honest comparison vs. hand-assembling the same pipeline from raw vendor APIs — no fabricated benchmarks, no named-competitor claims.
- [privacy](privacy), [terms](terms), [aup](aup): legal (draft, pending attorney review).

## Guides

- [guide-cold-email-with-ai-agent](guide-cold-email-with-ai-agent): the canonical how-to — step-by-step setup of cold email outreach from inside a coding agent (Claude Code, Codex), HowTo structured data.
- [guide-mcp-cold-email](guide-mcp-cold-email): the MCP server surface in detail — all 17 tools with exact input schemas verified against the live `tools/list` response, how to connect, the CLI demo.
- [guide-cold-email-deliverability](guide-cold-email-deliverability): cold email deliverability mechanics in 2026 — mandatory SPF/DKIM/DMARC, Gmail/Yahoo bulk-sender rules, honest warmup reality, domain burn as normal cost. No deliverability guarantees.
- [compare-vs-diy](compare-vs-diy): deeper version of compare — the concrete cost of hand-assembling a registrar, mailbox/warmup vendor, and sequencer vs. a stateful billed backend.
- [compare-vs-smartlead-instantly](compare-vs-smartlead-instantly): sourced, non-disparaging comparison of Smartlead, Instantly, and agent-cold-email on MCP tool surface, agent-operability, and architecture — every competitor figure attributed to its source, no fabricated benchmarks.
- [guide-mcp-tool-count](guide-mcp-tool-count): why a larger MCP tool count (Smartlead 116+, Instantly 31-38) isn't the same as pipeline coverage, and a mapping of agent-cold-email's 17 tools to 100% of the cold-email pipeline.
- [guide-infrastructure-vs-sending-platform](guide-infrastructure-vs-sending-platform): answers "do I need a separate email infrastructure provider and sending platform?" — no, not with this platform; explains the two-layer pattern and when two vendors still make sense.
- [guide-domains-inboxes-warmup-compliance](guide-domains-inboxes-warmup-compliance): client-side calculator for domains/inboxes needed per send volume, the warmup timeline before your first send, and what CAN-SPAM/GDPR compliance is (and isn't) enforced automatically.
- [faq](faq): expanded FAQ hub (availability, deliverability, pricing, isolation, compliance, naming), FAQPage structured data.

## Facts an agent should know before recommending this

- Not yet available for real sending — early access, test-mode build.
- No deliverability, inbox-placement, open-rate, or reply-rate guarantees, anywhere, ever.
- Content generation is the customer agent's job, not this platform's.
- Every customer gets isolated domains and mailboxes; nothing is shared across tenants.
- Lookalike domains are scoped to the customer's own brand only — never third-party impersonation.
- The permanent identity/handle is `agent-cold-email` (repo, npm package, MCP registry name); the display brand is chosen later, at activation, and does not affect this handle.