Features
The deliverability engine, in pieces.
A warmed sender pool, a reputation circuit-breaker, jurisdiction-aware routing, DNS automation, and compliance-grade suppression — all shipped, all exposed over the same REST API and MCP server.
Six pieces, one pipeline
Every shipped capability.
No roadmap items, no "coming soon" — everything below is live today and covered on its own page.
Warmed sender pool
A brand-new sending domain has no reputation, and receivers treat it with suspicion until it earns one. CogniLead maintains a managed pool of sending domains that are already warmed, jurisdiction-aware, and rotated by warmth — so a send never starts from zero.
See how it works →02Reputation circuit-breaker
Most cold-email tools tell you about a reputation problem after it has already cost you deliverability. CogniLead polls Google Postmaster Tools on a recurring schedule, evaluates each sending domain’s spam-rate and reputation signal against a fixed, documented threshold, and pauses that specific domain automatically the moment it crosses — no dashboard to babysit, no alert to react to by hand.
See how it works →03Jurisdiction-aware routing
Most cold-email tools process every lead through one pipeline regardless of where the lead — or the sender — is located. CogniLead reads a jurisdiction on every lead instead (an ISO 3166-1 country code, set explicitly on intake or derived from the source company’s country) and uses it three concrete ways: as an input to the legal-basis check for MarketPrior-sourced candidates, as the residency pin for the model that drafts the outreach, and as the filter that picks which warmed sending domain the email goes out from. Region is a property of how a lead is actually handled, not a line in a privacy policy.
See how it works →04REST API
Every part of the pipeline — leads, campaigns, sends, suppressions, webhooks, billing — is a real, documented HTTP endpoint under /api/v1, not an afterthought bolted onto a UI-first product. POST /api/v1/leads registers a lead and, when you pass a campaign_id, runs it straight through the pipeline: personalization, suppression, and dispatch over the warmed sender pool. From there, /api/v1/campaigns manages cadence and triggers runs, /api/v1/sends reads back per-lead dispatch history, and /api/v1/webhooks pushes delivery and reputation events to your own systems as they happen. The full contract — every path, method, request/response shape, and auth requirement — is generated from one route table into a single OpenAPI 3.1 document, published and browsable at /api/v1/docs.
See how it works →05MCP server
Run CogniLead from inside your AI IDE or agent loop — no dashboard tab required. @cognilead/mcp-server publishes the same pipeline behind the REST API and dashboard as a set of callable tools over the Model Context Protocol: four work with no API key so an agent can learn the surface immediately, eleven more unlock the real pipeline once you hand it a key, plus Resources for live read-only context and Prompts for ready-made playbooks. This page covers why it matters for an agent-driven workflow; see /mcp for the full tool, Resource, and Prompt reference plus install steps.
See how it works →06DNS automation
Authentication is the first gate any email passes before a receiver even reads it. Every domain in CogniLead’s managed pool is taken through registration, Cloudflare zone creation and nameserver delegation, and SPF/DKIM/DMARC record provisioning by one coded pipeline before it ever reaches the sending pool — no manual DNS panel, no copy-pasting host records, and no starter-policy DMARC that never gets tightened.
See how it works →07Compliance & suppression
A cold-email compliance program lives or dies on one question: does an opt-out, bounce, or complaint actually stop future sends, or does it depend on someone remembering to update a list? In CogniLead, suppression is a hard gate inside the pipeline itself — stage 2 of intersect() checks every lead's email against the suppressions table before it can reach personalization or dispatch, so a suppressed address cannot be re-mailed by any campaign, from any domain, ever, without someone explicitly reversing it. The list fills itself: RFC 8058 one-click unsubscribe clicks, mailbox-provider bounce and complaint feedback, and your own manual additions all land in the same table, checked the same way, every time.
See how it works →Underneath every send
Five mechanisms, always running.
None of this waits for you to check a dashboard — it runs continuously, in the background, on every domain in the pool.
Your leads deserve to reach an inbox.
Every email you send without protection is a gamble on whether it reaches the inbox at all. Bring your leads — CogniLead handles the warmup, the safety checks, and the cleanup, so you don't have to think about deliverability again.
100 sends a month, free forever · no credit card · cancel any time