Vencavo combines company and people research with workspace notes, saved searches, lists, and scoped developer access. The product implements REST and MCP contracts described in these guides.
Create an account at app.vencavo.com, verify your email, and create or select a workspace. The product origin is https://app.vencavo.com. The marketing website does not accept API credentials.
Choose your path
| Goal | Start here | Result |
|---|---|---|
| Research in the app | Use a workspace | Search, inspect, and save source references with team notes. |
| Build an application | Make your first REST request | Identify the workspace, search one page, and retry safely. |
| Connect an AI client | Connect through MCP | Authorize a client and inspect its workspace before spending. |
| Define a research set | Search filters and credits | Represent supported criteria and set a page budget. |
| Recover a failed call | Errors and limits | Correct inputs or retry without a duplicate paid operation. |
Know which records you are reading
Product directory responses carry source.mode and source.release. Preserve both with the returned record ID. A configured source and a labelled fixture are different evidence. Historical source observations do not prove current employment, contact deliverability, or complete coverage.
The public website uses fictional .example companies and people. Its explorers, JSON previews, CSV samples, and agent demonstrations run locally in the browser. Their identifiers and results cannot be used against a product deployment. Website sample fields describes that separate illustration.
Vencavo’s foundation has 299M+ contact records and 25M+ company records. These totals do not establish unique-person counts, completeness, accuracy, or coverage for your filters. Evaluate the fields you need.
Prepare access
Use a verified account with current workspace membership. Choose the workspace before research. Owners and admins manage workspace API keys. OAuth clients select a workspace and approve explicit scopes during consent.
REST and MCP share the same workspace credits and source data. A nonempty search page costs one credit, including a small page. Profiles, empty searches, and failed searches cost zero. Protected contacts require a separate quote and approval. Read search and credit semantics before a paid request.
Read documentation in your tools
Every guide has a Markdown link generated from the same source as its HTML page. llms.txt indexes those guides. llms-full.txt contains them together.
The configured product also serves /api/docs, /api/docs/quickstart, /api/docs/reference, and /api/openapi.json at its own origin. Use that deployment’s contract for client tooling. Authorized MCP connections expose embedded guides and current tool schemas. Public documentation discovery grants no data access.