Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.descovo.com/llms.txt

Use this file to discover all available pages before exploring further.

Descovo has multiple APIs that look similar on the surface but are optimized for different jobs. Calling the wrong one wastes credits, returns incomplete data, or fails entirely. Use this page to match your intent to the correct operationId before you build a payload — whether you are working through MCP or calling the API directly.

​
Quick decision matrix

Your intentBest APIWhyAvoid using
Discover many companies by filterscompanySearchOptimized for broad discovery across 47M+ companieskitchenSinkCompany for large-scale filtering
Deep data for one known companykitchenSinkCompanyReturns a rich, complete company profile in a single callcompanySearch when you already know the exact company
Discover people or prospects by role and companypeopleSearchOptimized for profile discovery across 847M+ profilessyncContactEnrichment for initial discovery
Reveal email or phone for a known profilesyncContactEnrichmentPurpose-built for contact detail revealpeopleSearch when you already have the profile
Fresh LinkedIn profile data for one personprofileLiveEnrichReal-time profile refresh for a specific individualpeopleSearch when freshness is the goal
Fresh LinkedIn company data for one companycompanyLiveEnrichReal-time company data refresh for a specific entitycompanySearch when freshness is the goal
Large enrichment or export workflowcreateAudience → buildAudience → triggerEnrichmentScales to hundreds or thousands of records; controls cost and progressRepeating sync calls one-by-one at scale

​
companySearch vs kitchenSinkCompany

These two endpoints both return company data, but they serve opposite purposes. Use companySearch when you need to discover companies. You provide filters — industry, headcount, country, funding stage, keywords — and get back a paginated list of matching companies. This is the right tool when you do not know which specific companies you want yet. Use kitchenSinkCompany when you already know which company you want. You provide a domain or identifier and receive a single, deeply enriched profile with all available fields in one response. This is the right tool when the user asks “tell me everything about Acme Corp.”
Do not use kitchenSinkCompany to browse or filter companies. It is not designed for discovery and will return incomplete or mismatched results for that use case.

​
peopleSearch vs syncContactEnrichment

These two endpoints both involve people data, but they operate at different stages of a workflow. Use peopleSearch to find people. You provide role titles, company names, locations, and seniority filters to discover professionals that match your criteria. Use this at the start of a prospect-building workflow. Use syncContactEnrichment to reveal contact details for people you have already identified. Once you have a profile from peopleSearch (or another source), pass it to syncContactEnrichment to retrieve verified email addresses and phone numbers. Do not call this endpoint speculatively on unknown profiles — it charges credits per lookup.
A common pattern: run peopleSearch to build a list, review it with the user, then call syncContactEnrichment only for the profiles the user confirms they want to contact.

​
Live enrich APIs vs search APIs

Descovo’s live enrich endpoints (profileLiveEnrich, companyLiveEnrich) fetch real-time data from LinkedIn for a specific entity. They are not interchangeable with the search APIs.
  • Search APIs (companySearch, peopleSearch) query Descovo’s indexed database. They are fast, support complex filters, and return results across millions of records. Use them for discovery.
  • Live enrich APIs bypass the index and fetch a fresh snapshot for one specific entity. Use them when the user explicitly needs up-to-the-minute data on a company or person they have already identified.
Using a live enrich API for discovery is slow and expensive compared to a search API. Use the right tool for the right job.

​
When to move from direct API calls to audience workflows

Direct API calls (search + sync enrich) are appropriate for small, interactive lookups — typically fewer than 50–100 records. Move to the audience workflow when:
  • The user wants to enrich hundreds or thousands of records.
  • You need to control cost before committing (estimate before charge).
  • The job will take longer than a few seconds and needs async progress tracking.
  • You want to keep large result sets in Descovo’s database rather than in the conversation context.
The audience workflow (createAudience → buildAudience → getAudienceStatus → estimateEnrichmentCost → triggerEnrichment → getEnrichmentStatus → exportCompanies / exportProspects) is designed for scale. For the full step-by-step, see Connect AI tools to Descovo via MCP.
As a rule of thumb: if the user asks you to “enrich a list” or “export results” and the expected record count is more than a few dozen, propose an audience workflow rather than looping sync calls.

​
MCP workflow recommendation

When you are using MCP tools and are unsure which API to call, follow this three-step pattern instead of guessing.
1

Search for the right endpoint

Call search_endpoints with a plain-English description of your intent and any constraints you have:
{
  "query": "reveal email and phone for a known LinkedIn profile",
  "constraints": {
    "requiresSync": true
  }
}
The tool returns ranked operationId recommendations with explanations. Pick the top result unless a constraint rules it out.
2

Inspect the schema

If the selected API has complex nested filters or you are unsure of required fields, call get_endpoint_details_full with the operationId:
{
  "operationId": "syncContactEnrichment"
}
Review required fields, optional parameters, rate limits, and credit costs before building your payload.
3

Execute the call

Construct your call_operation payload using the exact schema returned in the previous step. Check chargeInfo in the response and surface any costs to the user.