// fig. 01 — lead enrichmentPOST/enrich/profile

Lead Enrichment API
for AI agents.

Work email or profile URL in, a verified lead out: title, company, headcount, funding stage, plus professional email, personal email and phone as separate flags. The email enrichment surface behind inbound routing, CRM re-verification and scoring.

Start now See workflows →

// 01 · response

{
  "profile": {
    "id": "prof_PVXj1LZJg54zXKcnKNBusu8LgvJX5SYm5QYj",
    "first_name": "Sarah",
    "last_name": "Martinez",
    "headline": "VP Sales at Stripe",
    "location": "San Francisco Bay Area",
    "experience": "[ 4 positions, omitted here ]"
  },
  "work_email": "[email protected]",
  "personal_email": "[ returned when enrich_personal_email is set ]",
  "phone": "[ returned when enrich_phone is set ]",
  "credits_used": 2.5
}

Abbreviated on purpose · full schema in the API docsdocs →

// accepted inputs

[email protected]social.com/in/sarah-martinez-vpprof_PVXj1LZJg54zXKcnKNBusu8LgvJX5SYm5QYjramp.com@tomas_builds

↓ scaleREST · MCP · webhooks

800M+// profiles

75M+// companies

3// contact flags

Overview

// fig. 02 — definition

What is a lead enrichment API?

A lead enrichment API takes the little you know about a lead, usually a work email or a profile URL, and returns what your sales process actually needs: current title and employer, company size, industry and location, funding stage, and the contact data to reach them. It is the call behind inbound routing, CRM re-verification and lead scoring.

On DataForB2B the enrichment surface is two endpoints. Enrich Profile resolves the person: role, work history, professional email, personal email and phone number, each as its own flag. Enrich Company resolves the account: headcount, growth, funding rounds and investors. Both run in real time over REST or as MCP tools inside your agent.

Email in: a work email resolves to the person and, through their employer, to the company record.
Profile URL or ID in: the same person record, plus the professional email, personal email or phone as separate flags.
Domain in: Company Search with the domain column returns the account for 0.75 credit on cached data.
Everything is billed per data type requested. A form hydration that only needs title and company never pays for a phone number.

// key facts

Person: POST /enrich/profile
Company: POST /enrich/company · POST /search/companies
Auth: api_key header
Inputs: Work email, profile URL, public ID, encoded ID, X handle, domain
Contact flags: enrich_work_email · enrich_personal_email · enrich_phone
Delivery: REST · MCP tools · monitors to your webhook

Playbook

// fig. 03 — enrichment playbook

Four enrichment moves in production.

From inbound form hydration to nightly CRM re-verification: two endpoints, four jobs your stack runs against them the day you wire them in.

// fig. 03move

Hydrate inbound forms

A visitor types a work email. Your form calls enrichment, gets title, employer, headcount and industry back, and routes the lead with context instead of as a bare row.

// inputs

work emailcurrent_titlecompany sizeindustry

// shipsrouted with context

// fig. 04move

Re-verify the CRM before a send

Run stale CRM rows through Enrich Profile on a schedule. Current employer and title come back live, so anyone who changed jobs is flagged before the next campaign goes out.

// inputs

enrich_profileis_currentwork email

// shipscleaner next send

// fig. 05move

Complete the contact record

Start from a profile URL and request only the contact flags you need: professional email for sequences, personal email for re-engagement, phone for the SDR call list.

// inputs

enrich_work_emailenrich_personal_emailenrich_phone

// shipscontactable lead

// fig. 06move

Score the account behind the lead

Pass the lead's company to Enrich Company: headcount growth over 6 and 12 months, funding stage, last round, investors and open jobs feed your scoring model in one call.

// inputs

growthfundinginvestorsactive_jobs

// shipsML-ready features

Primitives

// fig. 07 — primitives

Person, company, agent.

Call the two enrichment endpoints directly over REST, or expose them as tools to your AI through MCP. Same data, same credit pool.

// fig. 07PERSON

// primitive

Enrich Profile

The person, then the contact.

Profile URL, public ID, encoded ID or X handle in. Full profile at 1.5 credits, professional email at 1 credit, personal email at 3, phone at 10, GitHub at 1. Only what you flag is fetched and billed.

POST/enrich/profile

// notes

five independent flags
real-time fetch
800M+ profiles

// fig. 08COMPANY

// primitive

Enrich Company

The account behind the lead.

Slug, company URL, ID or X handle in. Size, headquarters and offices, funding rounds, investors, headcount growth and active jobs out, for a flat 1.5 credits.

POST/enrich/company

// notes

funding + investors
growth signals
75M+ companies

// fig. 09AGENT

// primitive

MCP tools

Tool calls, no glue code.

The DataForB2B MCP server exposes enrich_profile and enrich_company next to search. Claude, Cursor or any MCP runtime picks the tool, passes the identifier and reads the record.

TOOLenrich_profile · enrich_company

// notes

Claude · Cursor · OpenAI
same credit pool
no schema to maintain

Compare

// fig. 14 — how it compares

Enrichment API, data vendor, or GTM platform.

Three ways to enrich a lead. Each fits a different team; this is where DataForB2B sits.

// criterion	DataForB2B Lead Enrichment	Enrichment vendors (Hunter, People Data Labs, Clearbit)	GTM platforms (Apollo, ZoomInfo)
Starting input	Work email, profile URL, public ID, X handle or domain. Search results hand you the IDs.	Email or name + domain, matched against the vendor's database.	Email or contact record inside the platform's own CRM model.
What comes back	Person record plus professional email, personal email and phone as separate flags; company record with funding, investors and growth.	A fixed enrichment payload; contact fields depend on the plan.	Fields mapped to the platform's contact and account objects.
Freshness	Fetched at request time from 20+ sources, so a job change shows in the response.	Refreshed on the vendor's crawl cycle.	Tied to the platform's database refresh.
Billing	Per data type on each call. No seat, no annual dataset licence.	Per match or per record, often with annual commitments.	Per seat plus credit bundles on the subscription.
Agent integration	MCP tools plus REST; monitors push job changes and funding events to a webhook.	REST; the agent wraps the call itself.	Native to the platform, built for human users first.

Vendor characteristics summarised from their public documentation as of September 2026; check each provider for current terms.

Endpoints

// fig. 10 — endpoints

The endpoints your stack will call.

Four routes, one credit pool. Most revenue teams start with People and Company Enrichment, then add the MCP server once their agent tooling is in place.

// fig. 10

People Enrichment API

Profile or handle to person record, plus professional email, personal email and phone as separate flags.

POST /enrich/profile

// fig. 11

Company Enrichment API

Slug, URL or ID to full firmographics: size, funding rounds, investors, growth, active jobs.

POST /enrich/company

// fig. 12

Company Data API

Domain lookups and account lists: filter domain = or domain in [...] over 75M+ companies.

POST /search/companies

// fig. 13

MCP Server

enrich_profile, enrich_company, search_people and search_company as native agent tools.

TOOL enrich_profile · enrich_company

Compliance

GDPR compliant

Full compliance with European data protection regulations. Your data privacy is our priority.

CCPA compliant

Adhering to California Consumer Privacy Act standards for maximum data protection.

Publicly available data

All data sourced from publicly available and verified sources, ensuring ethical collection.

FAQ

// fig. 20 — enrichment builders ask

Questions from revenue & ops teams.

Anything we missed? Talk to us.

Yes. A work email resolves to the person, and through their current employer to the company record. If you already hold a profile URL, public ID or X handle, pass that instead: it is unambiguous and resolves fastest. For a bare domain, use Company Search with a domain = condition.

Three, each behind its own flag on Enrich Profile: enrich_work_email for the professional email (1 credit), enrich_personal_email for the personal email (3 credits) and enrich_phone for the phone number (10 credits). Request only the ones the workflow needs; an inbound routing call usually needs none of them.

Per data type, per call. Profile 1.5 credits, professional email 1, personal email 3, phone 10, GitHub 1. A company enrichment is a flat 1.5 credits; a domain lookup through Company Search is 0.75 credit on cached data. There is no per-seat fee.

Batch your rows and call Enrich Profile with enrich_profile: true on a schedule; the current employer and title come back live. For accounts, Company Search with domain in [...] returns up to 1000 records per request. If you want to stop polling, create a monitor on the job change signal and let DataForB2B push the event to your webhook.

Enrichment fetches at request time and aggregates from 20+ sources, which is why a role change appears as soon as it is public. Company Search offers a cheaper cached mode with enrich_live: false when you only need stable firmographics on a large list.

Yes. DataForB2B processes publicly available professional data, offers a DPA and an opt-out process, and publishes its subprocessor list. That covers EU-deployed CRM enrichment and marketing automation use cases.

Get Started

// fig. ∞ — ship

Build with us. Now.

Get an API key in 60 seconds. Plug your AI agent into 800M+ verified profiles and 75M+ companies — today.

Get an API key Talk to founders

↓ nextREST · MCP · Webhooks

Lead Enrichment API
for AI agents.

What is a lead enrichment API?

Four enrichment moves in production.

Hydrate inbound forms

Re-verify the CRM before a send

Complete the contact record

Score the account behind the lead

Person, company, agent.

Enrich Profile

Enrich Company

MCP tools

Enrichment API, data vendor, or GTM platform.

The endpoints your stack will call.

People Enrichment API

Company Enrichment API

Company Data API

MCP Server

GDPR compliant

CCPA compliant

Publicly available data

Questions from revenue & ops teams.

Can I enrich a lead from a work email only?

Which contact fields can a lead enrichment return?

How is lead enrichment billed?

How do I re-verify a whole CRM?

Is the data fresh or cached?

Is it GDPR and CCPA compliant?

Build with us. Now.

Lead Enrichment APIfor AI agents.

What is a lead enrichment API?

Four enrichment moves in production.

Hydrate inbound forms

Re-verify the CRM before a send

Complete the contact record

Score the account behind the lead

Person, company, agent.

Enrich Profile

Enrich Company

MCP tools

Enrichment API, data vendor, or GTM platform.

The endpoints your stack will call.

People Enrichment API

Company Enrichment API

Company Data API

MCP Server

GDPR compliant

CCPA compliant

Publicly available data

Questions from revenue & ops teams.

Can I enrich a lead from a work email only?

Which contact fields can a lead enrichment return?

How is lead enrichment billed?

How do I re-verify a whole CRM?

Is the data fresh or cached?

Is it GDPR and CCPA compliant?

Build with us. Now.

Lead Enrichment API
for AI agents.