FAQ

Yes. Coldrig is live: the HTTP API, the hosted MCP server, the npm command-line tool, free test mode, and real sending from your Google Workspace mailboxes are all available today. Sign-up, billing, screening, and setting up real mailboxes are fully self-serve and automatic; we then finish authorizing each mailbox to send, so you don't wait in a queue or do anything. You can also run the full free demo at no cost — see the demo walkthrough — just make clear to a user which mode they're in.

In test mode, every domain purchase, mailbox, and send is simulated, so nothing is bought and no email reaches a real person. A live account gets real mailboxes and sends real email from your Google Workspace mailboxes. Checkout and billing (Stripe, real cards) are live and self-serve; getting from sign-up to a live account with real mailboxes is fully self-serve and automatic, and we then finish authorizing each mailbox to send. Your API key stays the same when you go live.

Real sending is live today. On the dashboard, press Go live on the Billing page. A connected agent can instead 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 the number of mailboxes you have set up (3-mailbox floor; each mailbox past the first three is $5/month). 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. Setting up your real mailboxes is then fully self-serve and automatic, and we then finish authorizing each mailbox to send.

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 the mailbox/warmup vendor'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 (on a domain Coldrig bought, a slowed mailbox stays at 5/day until it has two clean weeks, then climbs back; on your own domain it stays slowed) — 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. For mailboxes on domains Coldrig bought, if one goes unused for two months, or restarts after being stopped, Coldrig runs warm-up again for a month at no extra charge when it next sends. 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.

It depends on the path. A lookalike domain we register requires zero customer DNS work. Your own domain at an external registrar requires one nameserver change, made once. Your own domain on Cloudflare Registrar cannot have its nameservers changed at all — that's Cloudflare's own product lock — so only a token-connect path works there, and it's walled off. BYO mailboxes on your existing mail infrastructure mostly work with the DNS you already have. See the full matrix on the BYO domain page.

No. Writing the content is the job of your AI app or coding agent — 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 creates an account in test mode, where nothing real is bought or sent: the code that chooses between simulated and real services checks the account's plan first, and an automated test fails if that check is ever bypassed. Every domain purchase, mailbox, and send in test mode is simulated, including bounces, complaints, and replies, at no cost. On a trial account, a campaign you launch plays out by itself as a simulation, with no demo step and whatever its sending hours, and no email reaches a real inbox. Your API key stays the same when the account goes live. A free test-mode account that never goes live and goes unused for 90 days is removed, though none is removed before January 31, 2027. See the CLI demo details.

In ChatGPT, add the connection address https://api.coldrig.dev/mcp as a custom MCP server, choose OAuth, sign in to Coldrig, and press Allow; nothing is connected until you do, and there is no API key to copy. ChatGPT decides which accounts can add a custom server. Claude's connector settings (Customize, then Connectors) take the same address and sign-in, but we have not tried adding it by hand there, and in our test the Claude assistant in a free web chat could not add a server or call Coldrig itself. Steps for each app: Add Coldrig to Claude or ChatGPT. A coding agent such as Claude Code or Codex adds the hosted MCP server with one command or config line (streamable HTTP; you sign in to Coldrig in your browser, and your API key is the fallback), or calls 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 customers. Every authenticated call is scoped to exactly one account's data at the engine level, not just at the API layer. The one exception is the crowdfunding shared bounce list: crowdfunding accounts share a list of hashed addresses that hard-bounced or complained, so one organization does not mail an address another already found undeliverable. It holds no customer identity. See the Privacy Policy.

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: $49 a month covers your first 3 mailboxes, and each extra mailbox is $5 a month (3-mailbox minimum; no setup fee, no domain fee): 3 cost $49/month, 5 cost $59, 10 cost $84, 20 cost $134, and 60 cost $334. A mailbox counts while warming, send-ready, or health-paused because Coldrig is still reserving that capacity. Domains are included and sends are not separately metered. That price is all-in: mailbox seats, domains (registration and burn-replacement), warmup, the sending platform, and compliance infrastructure, with $0 per-send fees. The other tools on our comparison page bill the software plan, the mailboxes and the domains separately; it shows the totals at 3, 5, 10, 20 and 60 mailboxes. 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; sign-up, billing, screening, and setting up real mailboxes are fully self-serve and automatic, and we then finish authorizing each mailbox to send.

Your subscription is billed through Stripe. The Coldrig dashboard does not list invoices or receipts. For a question about a charge, email support@coldrig.dev.

On the dashboard Billing page, open Subscription actions and press Update payment method. It opens Stripe's secure billing page in the same tab, and you return to the dashboard when you are done. A connected agent can get the same page from POST /billing/portal.

This works only after the account has gone live, because the card is collected on the Stripe checkout page when you go live. If the billing page cannot open, try again later or email support@coldrig.dev.

The first payment is taken when you complete the Stripe checkout page that starts your subscription. The subscription is billed monthly, unless otherwise stated, to the card on file and renews automatically until canceled.

The amount follows the number of mailboxes set up on your account, never below 3 mailboxes ($49 a month). Mailboxes you add are prorated for the rest of the current billing period. Mailboxes you remove are released right away with no credit for the rest of the current billing period, and the lower price starts at your next renewal.

Going live starts when you pay on the Stripe checkout page. The account then reads billing as active (GET /account shows billingState). Setting up your real mailboxes after that is automatic, and we then finish authorizing each mailbox to send. Your account and API key stay the same.

Typically, first emails go out the same day you go live, or the next business morning, and each mailbox reaches full speed after about four weeks of warm-up. This is typical, not a guarantee.

Until real sending is live, the dashboard says so, and the sends it shows are simulated previews.

You can cancel on the dashboard Billing page (Subscription actions, then Cancel subscription), or your connected agent can call the /cancel endpoint. You can also email support@coldrig.dev to request cancellation on your behalf. On the dashboard the button is available once the account has a paid plan, you choose when it ends, and nothing happens until you confirm.

At the end of your billing period (the default): the account is marked canceling as soon as you confirm. Campaigns that are already running keep sending until the end of the period you paid for, then all sending stops (an account behind on a payment stops sending at once). Your mailboxes and domains are not released when you confirm.

Immediately: the account is marked canceled, campaigns stop, every mailbox is released right away and cannot be brought back, and domains we bought for you are released too (a domain you connected yourself is not touched).

A canceled subscription stops future renewal charges; we do not prorate or refund the unused portion of a billing period already paid for, except where applicable law requires it. See the Terms of Service.

API keys are stored only as a one-way hash, so they cannot be read back or emailed. To get back in, open the dashboard sign-in page and choose Email me a sign-in link instead. The Lost API key card on the support page links there.

Enter your account email. If an account exists for that email, a single-use sign-in link is sent to it. The link expires in 15 minutes and signs you straight into your dashboard. An email link opens the one account confirmed for that email. If the email isn't confirmed yet, the link asks once for the account's API key, to confirm the account is yours. When you create an account, we may email a link that confirms the address without the key if you open it in the browser where you're signed in to that account. If you have another account on the same email, you get into it with its API key. If you lost the key before that, email support@coldrig.dev and we'll help.

Once you are in, Settings has Rotate API key. It makes a new API key, shown once, and the old key stops working immediately. Every browser session for the account is signed out with it, and every connected app is disconnected. Then update your agent's connection with the new key.

Support is around the clock: email support@coldrig.dev any time with product, dashboard, billing, or cancellation questions. Include your account ID when it is safe to do so, and never email your API key. The support page lists the other routes, including security and abuse reports.

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 the footer of every campaign email, and every campaign email carries a List-Unsubscribe header (full RFC 8058 one-click unsubscribe, both the mailto and hosted-endpoint forms, honored immediately). A suppression list is enforced server-side on every send. Replies sent with the reply tool or the dashboard on an existing thread carry no footer and no List-Unsubscribe header. 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 use beyond test mode, the customer is the "sender" and "initiator" under CAN-SPAM and comparable laws; EpiphanyMade sets up 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.