Prospect Connect
The machine surface of a Prospect project: a JSON feed, signed webhooks, a scoped API, and the option to run each stage with your own tooling.
A Prospect project defines an offering and gathers candidates from a Market, a Watch or your own list. Its cycles are bounded, and each one qualifies a company, researches it against public sources and writes an opener grounded in that evidence. Prospect Connect is the same project, readable and drivable by a machine.
There is one prospect representation. Feed rows, API reads and webhook payloads all carry it, at schema version 2026-08-01. A webhook adds an envelope around it.
What you can do
- Read a project from a revocable JSON URL, or through the API.
- Be told when research is ready, an opener needs approval, a bundle is approved, work goes stale or a cycle finishes.
- Push companies in from a CRM segment or a Clay table, keeping your own row identifiers attached.
- Start bounded research under the project's budget and its one-active-cycle rule.
- Perform a step yourself. Qualification, research and outreach each choose between Prospex and your own tooling.
- Approve a named revision with the exact content fingerprint you reviewed.
What it will not do
- Match a company silently when the identity is ambiguous. You get the candidates back and no research is spent.
- Run the Prospex step when your worker fails, expires or never claims. Retry it, or change the executor and ask for new work.
- Treat retrieving an approved payload as having contacted anyone.
- Export raw page content or raw model output.
Start here
Open your project's Connect page in the app. It carries the feed URL, the webhook settings, a payload preview built from your own data, and a list of exactly which private fields leave your workspace.