[ DOCUMENTATION ]
CogniLead, documented.
The deliverability engine, end to end — architecture, content outbound email, lead intake, deliverability, the MCP surface, and the API.
6 sections · ~59 min end to end · updated 2026-06-04
Full API reference at /api/v1/docs
Outbound engine
3 sectionsOutbound email
Personalised, multi-step email sequences to the leads you supply. Delivery goes out over plain SMTP from pooled sender mailboxes (nodemailer under the hood); CogniLead owns the warmed sender pools, personalisation, the per-step cadence, and the outbound hygiene.
Read →Lead intake
The default path is still yours: you POST the leads and CogniLead verifies, de-dupes, suppresses, schedules, and sends them. A second, admin-triggered path can source leads from MarketPrior directly into a tenant, but only where a documented legal basis for cold-contacting exists.
Read →Deliverability & compliance
Healthy delivery through Resend, plus the only compliance surface CogniLead carries: a per-tenant suppression list and RFC 8058 one-click unsubscribe. Nothing more is sold or promised on compliance.
Read →Build & integrate
2 sectionsMCP server
The @cognilead/mcp-server brings CogniLead into Cursor, Claude Desktop, and Windsurf. Two free, capped content tools work with no key; the outbound tools (ingest a lead, run a campaign, suppress) are gated behind an API key.
Read →HTTP API
A narrow HTTP API under /api/v1 covering lead intake, sends, campaigns, suppression, billing, and reseller/customer surfaces. Authenticated with a single per-tenant pk_live_* API key or a Supabase SSR session.
Read →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