Brief result API
A future REST API will expose generated brief summaries, recommendations, sources, report modes, and export references so teams can move LeadBrief output into CRMs, proposal tools, or internal dashboards.
Docs
API and MCP docs are being shaped around real brief workflows.
The public documentation page is intentionally focused on integrations: how teams will connect generated LeadBrief results to CRMs, proposal tools, internal AI assistants, automation systems, and reporting workflows once API access opens.
MCP access
A future MCP server can let approved AI assistants list briefs, retrieve a report, search prospects, and pull structured opportunity data into agent workflows.
Scoped API keys
API keys should be scoped by workspace and capability, such as read briefs, create briefs, read prospects, or export reports. The product already keeps API-key schema space for this path.
Structured JSON
The brief output is designed around structured sections rather than raw paragraphs, making it easier to pipe summaries, questions, opportunities, and assumptions into other systems.
Planned interface
The useful integration is the one that moves the report where work already happens.
LeadBrief should not force teams to copy and paste forever. The planned API and MCP surfaces are built around stable IDs, workspace ownership, scoped access, and structured report data that can be consumed by other tools.
GET /v1/briefs
List completed briefs with pagination, status, website, business name, created date, and report modes.
GET /v1/briefs/{id}
Retrieve one brief as structured JSON with sources, opportunities, discovery questions, outreach copy, and proposal notes.
POST /v1/briefs
Queue a new brief from a normalized website URL, selected pages, analysis depth, and template instructions.
GET /v1/prospects
List saved prospects for a workspace so external systems can connect account records to generated briefs.
POST /v1/exports
Create a print-ready report export for a selected brief and report mode.
Webhook: brief.completed
Notify external systems when a queued brief finishes and is ready to sync.
Connection ideas
What external tools should be able to do with a discovery brief?
Send a completed brief to a CRM account timeline before a salesperson starts outreach.
Push proposal angles into a project intake tool for an agency strategist.
Let an internal AI assistant answer questions from saved LeadBrief reports.
Trigger a Slack or email notification when a high-priority prospect brief is ready.
Create a client-facing PDF after a team approves the internal research notes.
Attach discovery questions to a calendar event or sales call preparation note.
API and MCP access
Tell me what you need LeadBrief to connect with.
If your team wants CRM sync, an MCP server, report webhooks, or structured brief exports, join the waitlist and describe the integration workflow.
Free waitlist available
Optional $15 Founding Access
$15 in future LeadBrief credits