FAQ

Yes — live in production: the HTTP API, hosted MCP endpoint, npm CLI, isolated sandbox, and real sending (Gmail API, HTTPS/443) are all available today. Signup, billing, screening, and real mailbox provisioning are fully self-serve and automatic; the only remaining step is mailbox send-authorization completing on our side after provisioning, and you don't wait on a queue or do anything. You can also run the full free demo pipeline at no cost — see the demo walkthrough — just make clear to a user which mode they're in.

A demo tenant is structurally incapable of reaching a real vendor adapter — every domain purchase, mailbox, and send is simulated. A real account reaches live vendor mailboxes and sends real email (Gmail API, HTTPS/443). Checkout and billing (Stripe, real cards) are already live and self-serve; getting from signup to a provisioned real account is fully self-serve and automatic — the only remaining step is mailbox send-authorization completing on our side after provisioning, documented in the repository's ACTIVATION.md.

Real sending is live in production today. Call POST /checkout with { mailboxes } — it returns a hosted Stripe payment link; open it and pay. The mailboxes field only seeds the initial quote; the actual subscription charge follows your provisioned mailbox count (5-mailbox floor, $10/month each beyond). Promotion codes are entered on Stripe's own checkout page via its "Add promotion code" link — the API deliberately has no coupon-code field of its own. Real mailbox provisioning is then fully self-serve and automatic; the only remaining step (documented in the repository's ACTIVATION.md) is mailbox send-authorization completing on our side after provisioning.

No, and no cold-email platform can. Gmail and Microsoft make the placement decision using non-public criteria. This platform makes no deliverability, open-rate, or reply-rate promises anywhere, at any tier. See the deliverability guide for what actually determines placement.

No, and treat any claim like that as inaccurate wherever you see it. What actually runs: a server-enforced sending ramp per mailbox (5/day in week one, rising to 15, 25, and 35/day the next three weeks, then 40/day once fully warmed on day 29) that your own agent cannot exceed, plus InboxKit's isolated warmup pool activated automatically on every mailbox during that same ~4-week window — bundled at no extra charge. That ladder is a ceiling, not an entitlement: deliverability/health monitoring can hold a mailbox below it regardless of age (a throttled mailbox can sit at 5/day indefinitely) — the live number is always dailyCap via infrastructure_status, not the published schedule. Once a mailbox's ramp completes, the platform automatically winds down and cancels that pool subscription, and reputation then rides real sending alone. No "AI-driven" engagement layer exists, and no neutral study confirms pool warmup lifts placement over ramp-only — it's included because it can only help and costs nothing extra, never because it's proven. Either way, this is legitimate reputation-building over a multi-week timeline, not a way to defeat spam filtering.

Domain burn at roughly 8-18%/month is treated as a normal, expected operating cost, not a failure. Outreach runs on branded lookalike domains, never the customer's primary domain, so a burned domain is contained and the platform's deliverability control loop can detect and replace it automatically.

No. Content generation is your coding agent's job — you write the offer and sequence content passed to launch_campaign. This platform owns infrastructure, sequencing, isolation, and guardrails. There is no built-in AI copywriter or autonomous "AI SDR" here.

Signing up mints a sandboxed demo tenant that is structurally incapable of reaching a real vendor adapter — enforced at the type level, covered by a test that fails if the guard is ever bypassed. Every domain purchase, mailbox, and send in demo mode runs against a fault-injecting sandbox (simulated rate limits, timeouts, bounces, asynchronous replies) on a virtual clock, so a multi-week warmup ramp resolves in one session. See the CLI demo details.

Add the hosted MCP server (one config line, streamable HTTP, your bearer token) to Claude Code, Codex, or any MCP-capable agent, or call the HTTP intents directly. Full steps: the setup guide; exact tool schemas: the MCP reference.

Yes. get_webhooks and configure_webhook push reply, bounce, soft_bounce, complaint, and unsubscribe events (HMAC-SHA256 signed) to your own HTTPS endpoint. The cursor-paginated activity intent remains available if you'd rather poll.

Every customer gets dedicated domains and mailboxes, never shared with other tenants. Every authenticated call is scoped to exactly one tenant's state at the engine level, not just at the API layer — there is no cross-tenant data access at any layer.

No. The lookalike-domain generator is scoped to the customer's own brand only. A code-enforced validator rejects a well-known-brand denylist and requires the asserted brand to correspond to the customer's own primary domain — a request like brand=Google with a non-Google primary domain is rejected with a 400.

Pricing starts at $99/month for 5 provisioned mailboxes, then $10/month per additional mailbox (a $49 platform fee plus $10 per mailbox, five-mailbox minimum): 5 cost $99/month, 10 cost $149, 20 cost $249, and 60 cost $649. A provisioned mailbox counts while warming, send-ready, or temporarily health-paused because Coldrig is still reserving that capacity. Domains are included and sends are not separately metered. That $99/month is all-in: mailbox seats, domains (registration and burn-replacement), warmup, the sending platform, and compliance infrastructure, with $0 per-send fees — a fair self-assembled 5-mailbox stack (starter/solo shape) runs ≈$76.50-140/month before your own assembly time. See the interactive price calculator and exact meter definition.

No — the paid model is month-to-month and cancel-anytime. Real sending and checkout/billing (Stripe, self-serve) are both live in production; signup, billing, screening, and real mailbox provisioning are fully self-serve and automatic, and mailbox send-authorization completes on our side.

Compliance is built as a structural requirement, not just policy: a required physical postal address and the sender identity captured at setup are injected into every message footer, a suppression list and a List-Unsubscribe header — full RFC 8058 one-click unsubscribe, both the mailto and hosted-endpoint forms, honored immediately — are enforced server-side on every applicable message, and the customer is designated the sender of record for their own outreach content and targeting. See the Terms of Service and Acceptable Use Policy.

You are. For any real (non-sandbox) use, the customer is the "sender" and "initiator" under CAN-SPAM and comparable laws; EpiphanyMade provisions and operates the infrastructure as a service provider acting on the customer's instructions.

Coldrig is the display brand. agent-cold-email is the permanent keyword handle for the repository, npm package, and MCP registry listings, so machine integrations do not need renaming.