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.

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 →02

Reputation circuit-breaker

Most cold-email tools warn you about reputation problems after the fact. CogniLead watches Google Postmaster Tools signals continuously and automatically pauses a specific sending domain the moment it drifts, before the damage compounds.

See how it works →03

Jurisdiction-aware routing

Most cold-email tools process every lead through a single pipeline regardless of where the lead — or the sender — is located. CogniLead routes processing on a jurisdiction-aware basis instead, so data residency is a property of the system, not an afterthought.

See how it works →04

REST API

Bring leads in and send through the same programmatic surface: POST /api/v1/leads to register a lead, then a send endpoint that runs the lead through suppression and the warmed pool. The full contract is documented as an OpenAPI 3.1 spec at /api/v1/docs.

See how it works →05

MCP server

@cognilead/mcp-server publishes CogniLead 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, twelve more unlock the real pipeline once you hand it a key. This page is a quick overview; see /mcp for the full tool, Resource, and Prompt reference.

See how it works →06

DNS automation

Authentication is the first gate any email passes before a receiver even reads it. Domains in CogniLead’s managed pool ship with SPF, DKIM, and DMARC already provisioned correctly — no manual DNS record setup on your end.

See how it works →07

Compliance & suppression

Every send passes through a suppression check before dispatch, and every outbound email ships RFC 8058 one-click unsubscribe by default. Opt-outs and bounces are honored automatically — there is no separate suppression list to maintain and remember to apply.

See how it works →