Cold-email deliverability — global, compliant, managed
For B2B teams that bring their own leads: CogniLead runs the deliverability ops that keep cold email in the inbox — warmed sender pools, a reputation circuit-breaker, and reply, bounce, and unsubscribe handling honored in the send path. You send; we keep you out of spam.
100 sends a month, free forever — no credit card.
Jurisdiction-aware pool, peer-to-peer warming, warmth rotation.
Auto-pauses a domain on Postmaster spam-rate drift.
Personalised over Resend, suppression-aware, reply + bounce tracked.
One managed engine — warmed pools, reputation guard, and suppression-aware sends over Resend.
Built on the infrastructure that runs the deliverability engine
CogniLead delivers outbound email through Resend, drafts copy with phi-cloud, bills on Stripe, and runs multi-tenant on Supabase. Product and brand names belong to their respective owners.
The delivery loop
You bring the leads; CogniLead runs everything between them and the inbox. Each step below is an event in one managed queue — gate-checked at send time, retried on failure, and observable end to end.
Leads enter through one API call — POST /api/v1/leads — from your CRM, scraper, or an Apollo / Clay export. CogniLead verifies, de-dupes, and suppression-checks each one before it ever enters a sequence.
POST /api/v1/leads
[{ email, name, jurisdiction }]
→ verified, de-duped, suppressedA jurisdiction-aware pool of warmed sender domains, kept healthy by a peer-to-peer warming engine where pool mailboxes warm each other. Sends rotate by warmth so no single domain gets hammered.
pickRegion(lead.jurisdiction) → warmest sender domain // peer-to-peer warming
Draft the sequence copy with phi-cloud — structured LLM generation that returns short, on-message steps as strict JSON. Useful scaffolding you edit and own, not a content suite.
phiCloud.chat.completions.create({
task: 'outbound.personalize',
response_format: { type: 'json_object' },
})A DB-backed, idempotent scheduler runs the sequence and re-checks every gate — suppression, reputation, warmth — before each step. No pre-baked blast queue; each send is decided at send time.
scheduler.tick() // re-check gates per step dispatchStep(send)
Resend runs the sequence over HTTP or SMTP. IMAP reply correlation pulls answers back to the lead; webhook bounce handling suppresses hard bounces immediately and soft bounces after 3-in-14-days.
resend.emails.send({ to: lead.email, ... })
// IMAP reply correlation
// hard bounce → suppressA Google Postmaster monitor auto-pauses any sender domain on spam-rate or reputation drift, plus suppression as a hard gate and RFC 8058 one-click unsubscribe on every send. That’s the hygiene — nothing more promised.
postmaster.poll(domain) if (spamRate > limit) pause(domain) List-Unsubscribe-Post: One-Click
The wedge
Smartlead and Instantly hand you a queue and a warming toggle. CogniLead ships warming, reputation monitoring, and gate-checked scheduling as first-class infrastructure — the operations layer that keeps cold email out of spam, in any region. You bring the leads; this is the part that’s hard to run yourself.
A peer-to-peer warming engine keeps pool mailboxes warming each other, and the send path rotates by warmth. Most tools bolt warming on; here it’s in the delivery loop.
A Google Postmaster monitor watches spam rate and reputation and pulls a degrading sender domain on its own — before one bad campaign drags the whole pool into spam.
Sender pools and processing map each lead to its region — EU, UK, US, CH, APAC and beyond. Data-residency-aware by default, so “where does this run” has a real answer wherever you sell.
Outbound hygiene
Good outbound starts with good hygiene. Every email ships with one-click unsubscribe, a per-tenant suppression list keeps opt-outs and bounces out of every send, and a reputation circuit-breaker pulls a degrading domain before it drags the pool down.
RFC 8058 List-Unsubscribe and List-Unsubscribe-Post headers on every email. Recipients opt out in a single tap, straight from their inbox.
Unsubscribes hit the suppression list within seconds — per-email and per-domain. Once suppressed, an address is never contacted again.
A Google Postmaster monitor auto-pauses any sender domain when its spam rate or reputation drifts — so one bad campaign can’t torch the whole pool. Hard bounces and opt-outs are filtered before every batch.
Built for builders
CogniLead is API-first — and the only deliverability engine in the category with a published MCP server, so your AI agent can send compliant outbound directly. No UI to live in unless you want one.
Clean /api/v1 surface — OpenAPI 3.1, Bearer keys, RBAC. Push leads, run sequences, read sends and suppressions from your own stack.
@cognilead/mcp-server drops the engine into Cursor, Claude Desktop, and Windsurf. Free scaffolding tools keyless; outbound tools gated by an API key.
Every endpoint and gate is written up in the spec — cited to how the backend actually behaves, so you can integrate without guessing.
curl https://cognilead.ai/api/v1/leads \
-H "Authorization: Bearer pk_live_…" \
-d '[{ "email": "cto@acme.com",
"name": "Dana",
"jurisdiction": "eu" }]'
# → verified, de-duped, suppression-checked,
# queued into a warmed, region-matched poolPricing
Pick the base bundle that matches your volume — warmed pools, reputation circuit-breaker, reply/bounce handling, and content scaffolding included. Past the bundle you pay per outbound send, never per seat.
FAQ
The short, honest answers on how the growth engine actually works.
It runs the deliverability operations for your cold email: warmed sender-domain pools, a Postmaster reputation circuit-breaker that auto-pauses degrading domains, a DB-backed scheduler that re-checks every gate before each send, IMAP reply correlation and bounce handling, and suppression with RFC 8058 one-click unsubscribe. You bring the leads; we keep the mail out of spam. AI content scaffolding (beta) drafts the copy.
You supply them. Leads enter through one API call — POST /api/v1/leads — from your CRM, a scraper, or an Apollo/Clay export. CogniLead is the deliverability layer downstream of wherever you source leads; it does not build or sell a contact database.
That is the product. Sends go over Resend (HTTP or SMTP) from a jurisdiction-aware pool of warmed domains, rotated by warmth. A Google Postmaster monitor auto-pauses any domain whose spam rate or reputation drifts, the scheduler re-checks suppression and reputation before every step, and every email ships an RFC 8058 one-click unsubscribe with the opt-out honored automatically.
A structured LLM call through phi-cloud (POST /api/v1/seo/generate) that drafts sequence steps and page copy from a product, topic, and keyword set. It is useful scaffolding you edit and own — not keyword research, SERP analysis, or an SEO intelligence product. It is in beta.
Below your tier cap (e.g. 10k on Growth) sends are covered by the base fee. Past the cap we report each send to Stripe at the tier overage rate ($0.035 on Growth) and you see the projected charge live on the dashboard. No surprise invoices — set a hard cap in /dashboard/billing.
No. You supply the leads (via the dashboard or POST /api/v1/leads) and CogniLead runs the deliverability — warmed pools, personalisation, suppression, and one-click unsubscribe. We do not build, enrich, rank, or sell a company universe; we are the layer downstream of your CRM, scraper, or Apollo/Clay export.
Still have a question? Read the spec or email us.
Bring your leads; CogniLead runs the deliverability ops that land them in the inbox. Start on the free tier — 100 sends a month, no credit card — and upgrade when you scale.