Solutions
Automated Dedicated IP Warm-Up — No Manual Schedule Required
Automated dedicated IP warm-up on Mails.ai means you add a dedicated IP ($50/mo, Scale tier or above) and SES manages the entire reputation ramp without a manual schedule. There are no seed lists to configure, no daily volume caps to track by hand, and no separate warmup service to purchase. The ramp runs alongside real transactional sends and completes in roughly 14 days.
Why warmup is usually a manual problem — and why it isn’t here
Most email providers hand you a fresh dedicated IP and a warmup guide: start at 500 sends on day one, double every few days, avoid spikes, manage the ramp yourself for four to six weeks. You either build a volume throttle into your application or pay a warmup service to run seed-network sends on your behalf.
Mails.ai skips that loop. When a dedicated IP is provisioned, the SES configuration set takes over the ramp — routing sends through both the new IP and the established shared pool until the dedicated IP has enough history to stand on its own. You do not write a warmup scheduler, configure seed addresses, or touch anything.
What the automated warm-up looks like in practice
From your application’s perspective, nothing changes. You call the same POST /v1/messages endpoint. SES decides whether each message goes through the dedicated IP or the shared pool during the ramp, optimising for deliverability on both. The split shifts toward the dedicated IP as its reputation builds.
# 1. Add the dedicated IP add-on (done via dashboard or on request for Scale+)
# 2. Verify (or reuse) your sending domain
curl https://api.mails.ai/v1/domains/yourapp.com \
-H "Authorization: Bearer $MAILS_API_KEY"
# { "status": "active", "dedicated_ip": "198.51.100.42", "ip_warmup": "in_progress" }
# 3. Send normally — warmup routing is transparent
curl https://api.mails.ai/v1/messages \
-H "Authorization: Bearer $MAILS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "notifications@yourapp.com",
"to": "user@example.com",
"subject": "Your invoice is ready",
"text": "Hi — your invoice is attached."
}'
# 202 Accepted — SES handles dedicated-IP vs shared routing automatically
# 4. Check warmup progress
curl https://api.mails.ai/v1/domains/yourapp.com \
-H "Authorization: Bearer $MAILS_API_KEY"
# { "ip_warmup": "complete", "reputation": 0.92 } ← after ~14 daysDedicated IP isolation vs. the shared pool
A dedicated IP does not improve deliverability on its own — it isolates your reputation from other senders. On the shared pool, the collective track record is already warm and well-maintained (per-agent reputation scoring, per-sender complaint auto-suspend, and outbound classification keep the shared estate clean). A dedicated IP makes sense when you want that reputation to be yours alone: other customers’ behaviour cannot affect your inbox placement, and your behaviour cannot affect theirs.
The automated warmup ensures that isolation starts clean: the dedicated IP earns its track record from your real transactional mail, not synthetic seed sends or borrowed history.
Pricing and availability
Dedicated IP add-on: $50/mo per IP, billed in advance. Available on Scale tier or above. Multiple IPs are supported — useful for multi-region sending or per-agent reputation separation. Provisioned per request until self-serve one-click shipping. Remove anytime, no contract.
The Metered tier (starts at $0/mo, $0.001 per message) includes automatic warmup for custom domains on the shared pool. Upgrade to Scale or above to add a dedicated IP with the same fully-automated ramp.
Frequently asked questions
Do I need a separate IP warmup tool?
No. When you add a dedicated IP on Mails.ai, the SES configuration set manages its reputation ramp automatically. There is no seed network, no warmup CSV, and no third-party warmup subscription required. The process runs alongside real sends from the day the IP is provisioned.
How does the automated warmup actually work?
SES routes sends through both the newly assigned dedicated IP and the existing warm shared pool during the ramp period. This builds a clean sending history for your dedicated IP without you having to throttle volume or engineer a warm-up sequence in code. You watch status in /dashboard/domains — no action required.
How long does dedicated IP warmup take?
Typically 14 days for a new dedicated IP. The exact timeline depends on your actual sending volume during that window. Higher consistent volume shortens the ramp; very low volume may extend it, which is true of all dedicated IP providers — SES-managed automation handles the routing, but the underlying signal is your real mail.
What if I already have a dedicated IP elsewhere with warmup done?
BYO IP is not available at Phase 1 (SES BYOIP requires AWS Direct Connect and is Phase 3 roadmap). Dedicated IPs are provisioned from AWS SES and carry SES-managed warmup automatically. If you are migrating from a provider where your IP was already warm, plan for a 14-day ramp on the new IP.
Is a dedicated IP required for warmup to work?
No. Even without a dedicated IP, new sending domains ramp automatically on the shared pool. A dedicated IP is for teams that want their inbox placement fully isolated from other senders — not a prerequisite for any use case. Most transactional senders do well on the shared pool.
What does a dedicated IP cost?
$50/mo per IP, billed monthly in advance via Stripe. Available on Scale tier or above. Add multiple IPs for multi-region sending or per-agent reputation isolation. Cancel anytime — no contract.
Built for agents.
Self-serve in minutes.
The API is live and self-serve. Drop ~6 lines into your agent and ship.
$ npm install @mailsai/sdk