vencavoPricingSign inGet started
FOR APPLICATIONS / DATA INTEGRATION

Company data API. Build on your workspace.

Search companies and people, inspect profiles, build lists, and unlock contact evidence through the same workspace as your app. Connect with a scoped API key.

Create your workspace Make your first API request
THE ENRICHMENT WORKBENCH · Illustrative preview
FICTIONAL PAYLOAD / DESIGN EXAMPLE

A record your product
can reason about.

Clear names. Explicit employee ranges. A source label that stays with the result. Unknown verification dates remain null.

Read the field definitions ↗Try the local domain lookup ↗
ILLUSTRATIVE COMPANY RESULT
{
  "company": "Forma Labs",
  "domain": "forma.example",
  "industry": "SaaS",
  "location": "San Francisco, US",
  "employees": "51–200",
  "source": "fictional-preview",
  "production_verified_at": null
}
DESIGN PRINCIPLES

Predictable records. Deliberate contracts.

  1. 01

    Resolve the entity

    Use the source ID returned by search to inspect the intended company. Keep that identity beside your saved research.

  2. 02

    Make gaps explicit

    Keep unavailable fields and unresolved domains recognizable. A missing result must not become fabricated context.

  3. 03

    Define the operating contract

    Follow the documented scopes, pagination, rate limits, and retry rules. The app, REST API, and MCP share your workspace balance.

BEYOND THE HAPPY PATH

Useful context includes
the edges of what is known.

These fictional states illustrate client behavior. Read the implemented error and retry contract for your workspace.

01
MATCHED

A usable record

Display the company identity and available fields. Keep source context beside the values.

forma.example → Forma Labs
02
NO MATCH

An unresolved identity

Ask for a better identifier or leave the account unresolved. A missing result is not a fabricated profile.

unknown.example → no sample match
03
MISSING FIELD

A visible unknown

Preserve unavailable values. Do not turn missing revenue or dates into zero or today.

production_verified_at → null
04
SERVICE ERROR

A deliberate recovery

Use the documented error and retry rules. Preserve the same operation key when retrying an uncertain paid request.

Correct invalid input; retry temporary failures safely
Explore provenance and missing-value rules ↗

Choose your next step.

All developer resources ↗
Create your workspaceMake your first REST requestExplore MCP integration

A few useful details.

How do I get an API key?

Create an account, verify your email, and create or select a workspace. Open API keys in the app, choose the permissions and expiry your integration needs, and follow the REST quickstart. Never put a secret key in browser code.

Are the examples live API responses?

No. The website payloads use fictional records. Use a verified workspace account at app.vencavo.com to make authorized requests with the developer guides.

Should I use the API or MCP?

Use REST when your application owns the request flow. Use MCP when an AI client will choose supported tools. Both use the same workspace permissions, credit balance, source records, and lists.

BUILD WITH CONTEXT

Small, clear contracts.
More useful applications.

Read the implemented REST and MCP contracts, supported filters, and workspace permissions before connecting your client.

Create your workspaceRead the setup guide 100 welcome credits for eligible founders. No card needed to create an account.