// products
People Search APIPeople Enrichment APICompany Data APICompany Enrichment APILLM Data APISales MCP Server
// solutions
AI SDR APISales AutomationCandidate SourcingVC Data APILead EnrichmentBuying Signals
// explore
FeaturesIndustriesPricingCompliance
Sign inStart for free
// fig. 01 — lead enrichment api for ai

Lead enrichment API
for AI agents.

Profile URL or email in, 90+ datapoints out. Verified emails, current role, full firmographics — tool-call native for Claude, OpenAI and Cursor.

Try the API for freeSee workflows →
↓ enrichment surfaceREST · MCP · webhooks
90+// datapoints
200ms// p50 enrich
live// refresh mode
Playbook
// fig. 02 — enrichment playbook

Four enrichment moves in production.

From inbound form hydration to nightly CRM re-verification — same endpoint, four jobs your stack runs against it the day you wire it in.

// fig. 02move

Hydrate inbound forms

Visitor types an email. Your form calls our enrichment endpoint. Title, company, headcount, industry come back in 200ms so the lead gets routed with context, not as a bare row.

// inputs
work_emailtitlecompany_sizeindustry
// shipsinstant inbound routing
// fig. 03move

Re-verify your CRM

Pipe stale CRM rows through enrichment on a schedule — current title, current company, verified email. Mark anyone who left as inactive before the next campaign.

// inputs
is_currently_employedverified_emailcurrent_title
// shipscleaner next send
// fig. 04move

Turn a profile URL into structured data

Profile URL in, 90+ fields out: career history, education, current role, verified business email, social activity. Wire it into the CRM card or the lead-detail view.

// inputs
profile_urlcareer_historyverified_email
// shipsURL → 90+ datapoints
// fig. 05move

Score leads automatically

Pull company headcount, funding stage, tech stack and decision-maker title in one enrichment call. Push the JSON to your scoring model.

// inputs
funding_stageheadcounttech_stacktitle_seniority
// shipsML-ready feature payload
Primitives
// fig. 06 — primitives

Three primitives, one enrichment surface.

Person, company, agent. Call them directly via REST, or expose them as tools to your AI through MCP — same dataset, three integration shapes.

// fig. 06PERSON
// primitive

Profile URL or email → person

90+ datapoints in 200ms.

Career history, education, skills, verified business email, current role, location, social activity. Real-time mode crawls live at request time when freshness matters.

POST/v1/people/enrich
// notes
  • URL or email input
  • real-time refresh
  • verified emails
// fig. 07COMPANY
// primitive

Domain → full firmographics

Headcount, funding, tech, hiring.

Domain in, structured firmographic record out. Headcount, funding stage and history, tech stack, industry, locations, hiring activity.

POST/v1/companies/enrich
// notes
  • 50+ firmographics
  • tech-stack detection
  • hiring signals
// fig. 08AGENT
// primitive

Natural-language enrichment

Tool-call from any agent.

Drop the MCP server into Claude or your scoring agent. The model picks the enrichment tool, calls it, reads the response.

TOOLenrich_profile · enrich_company
// notes
  • Claude · OpenAI · Cursor
  • tool-call native
  • no glue code
Endpoints
// fig. 09 — endpoints

The endpoints your stack will call.

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

// fig. 09

People Enrichment API

Profile URL or email → 90+ datapoints. Career, skills, education, verified contact.

POST /v1/people/enrich
// fig. 10

Company Enrichment API

Domain → full firmographic record. Headcount, funding, tech, locations, hiring.

POST /v1/companies/enrich
// fig. 11

Agentic Search API

Natural language → verified results. Skip query construction; describe the lead.

POST /v1/agentic/search
// fig. 12

MCP Server

Native enrichment tools for Claude, Cursor and OpenAI agents.

TOOL enrich_profile · enrich_company
Compliance
GDPR Logo

GDPR compliant

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

CCPA Logo

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. 13 — enrichment builders ask

Questions from revenue & ops teams.

Anything we missed? Talk to us.

LinkedIn profile URL, work email, personal email, name + company, or domain (for company enrichment). Any of those will return the full structured payload — pick the input you have, we resolve the rest.

Standard cached responses are typically refreshed within 30 days. Real-time mode crawls live at the moment of the call and returns fresh data with a small latency premium — recommended for high-stakes inbound routing or pre-meeting briefs.

Yes. Every email returned passes a multi-step verification check (syntax, MX, deliverability, role-based detection). We don't return guesses — if we can't verify, we don't ship the field.

Two options. Async batch endpoint accepts arrays of records and returns a job ID; webhook fires when results are ready. Or stream records through the synchronous endpoint at our published rate limits — most CRMs do nightly enrichment runs this way.

Yes. Public sources only, signed DPA, opt-out endpoint, full subprocessor list published. Required for EU-deployed marketing automation and CRM enrichment 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 keyTalk to founders
↓ nextREST · MCP · Webhooks