# Enrichments

> Enrichments is a B2B data enrichment platform. It finds people and companies and returns work emails, job titles, seniority, department, location, LinkedIn URLs, company domains and firmographics, with email deliverability checked as part of the run. Results are delivered through a REST API, an MCP server, an in-product chat agent, and CSV upload, and credits are only charged for data that is actually returned.

## Key facts

- Surfaces: REST API, MCP server, Chat agent, CSV upload — one credit balance and one validation layer behind all four.
- People fields returned: email, linkedin_url, title, seniority, department, location, country, company, company_domain, headline, phone, company_profile.
- Company fields returned: company, company_domain, linkedin_url, location, country, headline, plus firmographics carried at no extra charge (industry, employeeCount, employeeRange, foundedYear, logoUrl, revenueAnnualUsd, fundingTotalUsd, latestFundingRound, monthlyVisits).
- Mobile numbers are available as the `phone` field and billed per number found. 15 common aliases — mobile, cell, direct dial, telephone and the rest — resolve to it rather than failing. Unlike an email address a number carries no deliverability verdict, because nothing checks a phone the way a mailbox can be checked.
- A phone number being available is not advice that it is lawful to call. Obligations under TCPA, DNC registries and local consent rules are the caller's.
- The field catalogue is closed. A request for anything outside the 12 people fields is a validation error, not an empty column.
- Email addresses are work addresses found from public sources. Personal contact details are not part of the catalogue.
- Enrichment is live rather than a licensed static database, so the same query can legitimately return different data tomorrow.
- Credits are charged only for data that is actually delivered. A lookup that returns nothing costs nothing.
- An enrichment row is charged only when at least one of the fields you asked for was resolved by us. Identifying somebody without adding any of them is free, and an identifier you supplied that comes back unchanged was never a resolved field.
- A search is charged per person or company returned, because there the identity is the delivered unit.
- A repeated question inside its cache window is charged at zero.
- A retry is free ONLY when it carries the same `Idempotency-Key` header as the original request. Without that header a retry is a new request: it creates a second job, takes a second hold, and is charged. Never describe a request as retry-safe without naming the header.
- Every charge is written to an append-only usage ledger you can read line by line.
- MCP endpoint: https://www.enrichments.io/api/mcp — Streamable HTTP, authenticated with an API key as `Authorization: Bearer`.

## Product

- [Overview](https://www.enrichments.io): What the product does, and the questions buyers ask most often.
- [MCP server](https://www.enrichments.io/mcp): Endpoint, tool list and client setup for Claude, ChatGPT, Cursor and Codex. 7 tools.
- [API reference](https://www.enrichments.io/docs): The REST contract: the 12-field catalogue, endpoints, errors and what gets charged.
- [Pricing](https://www.enrichments.io/pricing): Plan allowances and the price of every billable unit, with the delivered-only billing rule explained.

## API

- [OpenAPI 3.1 document](https://www.enrichments.io/api/v1/openapi): Generated from the schemas the routes validate with. No API key required to read it.
- `POST /api/v1/people/search`: Find people matching an ideal-customer profile. `query` carries the natural-language intent; every filter is optional. `fields` defaults to identity only — no address is looked up unless you ask.
- `POST /api/v1/people/enrich`: Resolve up to 100 identities — a LinkedIn URL, an email, or a name plus employer — into full person records. This is where work email addresses come from.
- `POST /api/v1/companies/search`: Find companies matching firmographic filters and a natural-language query.
- `POST /api/v1/companies/enrich`: Resolve up to 100 domains, names or LinkedIn URLs into company records.
- `GET /api/v1/jobs/{id}`: Poll a job. Always answers 200 — read `job.status`. `results` is null until the job is terminal, then pages with an opaque forward-only cursor.

## Writing

- [Blog](https://www.enrichments.io/blog): Index of everything published.
- [Lead Routing Data Requirements for Reliable Handoffs](https://www.enrichments.io/blog/lead-routing-data-requirements): Lead routing data requirements define the fields, normalisation rules, ownership logic, and fallback paths needed for dependable handoffs across sales teams.
- [How to Enrich a CSV of Leads Without Damaging CRM Data](https://www.enrichments.io/blog/enrich-csv-leads-safely): Learn how to enrich a CSV of leads with clean identifiers, careful column mapping, cost review, and export checks before controlled CRM updates.
- [Firmographic Data Explained for Better Account Decisions](https://www.enrichments.io/blog/firmographic-data-explained): Firmographic data explained: learn which company attributes matter, how they differ from contact data, and how to use them in account workflows.
- [Enrichment Credits Pricing Models for B2B Data Teams](https://www.enrichments.io/blog/enrichment-credits-pricing-models): Compare enrichment credits pricing models and learn how result-based billing, field selection, caching, and usage records support predictable data work.
- [GDPR B2B Contact Data: A Practical Operations Guide](https://www.enrichments.io/blog/gdpr-b2b-contact-data): Use GDPR B2B contact data responsibly with a practical workflow for lawful-basis review, transparency, minimization, and suppression handling.
- [Idempotency Keys API Design for Reliable Enrichment Jobs](https://www.enrichments.io/blog/idempotency-keys-api-design): Learn idempotency keys API design patterns for enrichment jobs, including retry handling, response recovery, and safeguards against duplicate charges.
- [Batch Enrichment vs Real Time: Choose the Right Workflow](https://www.enrichments.io/blog/batch-enrichment-vs-real-time): Compare batch enrichment vs real time workflows for CRM cleanup, lead routing, and live research, with a decision framework for each data trigger.
- [Email Bounce Rate Cold Outreach: A Practical Response Plan](https://www.enrichments.io/blog/email-bounce-rate-cold-outreach): Use email bounce rate cold outreach signals to diagnose list, domain, and mailbox issues, decide what to pause, and protect future sending quality.
- [How to Measure Data Quality for Trusted GTM Records](https://www.enrichments.io/blog/measure-data-quality-gtm-records): Learn how to measure data quality across completeness, validity, freshness, and consistency, then prioritize CRM repairs with a field-level scorecard.
- [How to Deduplicate CRM Records Without Losing Sales Context](https://www.enrichments.io/blog/deduplicate-crm-records-sales-context): Learn how to deduplicate CRM records with matching rules, merge decisions, field provenance, and safeguards that preserve sales context during cleanup.
- [Catch-All Email Domain Meaning Explained for B2B Outreach](https://www.enrichments.io/blog/catch-all-email-domain-meaning): Understand catch all email domain meaning, why mailbox checks can be inconclusive, and how to set cautious outreach rules for those addresses.
- [How to Find Someone's Work Email for B2B Outreach](https://www.enrichments.io/blog/find-work-email-b2b-outreach): Learn how to find someone's work email from public professional signals, check deliverability, and maintain accurate, compliant B2B outreach records.
- [B2B Data Enrichment Tools for Controlled CRM Updates](https://www.enrichments.io/blog/b2b-enrichment-controlled-crm-updates): Learn how B2B data enrichment tools support controlled CRM updates with field rules, review queues, validation, and audit-ready workflows.
- [Product Data Enrichment for B2B Data Operations](https://www.enrichments.io/blog/product-data-enrichment-b2b): Learn where product data enrichment fits in B2B operations, which data belongs in your GTM system, and how to avoid mixing entity types.
- [Job Title Normalization for Reliable GTM Data and Routing](https://www.enrichments.io/blog/job-title-normalization-gtm-data): Learn job title normalization methods, mapping rules, and governance practices that make segmentation, routing, and reporting more reliable across your CRM.
- [How to Build an ICP With Data for Better Account Targeting](https://www.enrichments.io/blog/build-icp-with-data): See how to build an icp with data by choosing useful signals, defining exclusions, and turning your criteria into repeatable account selection rules.
- [What Is an MCP Server? A Practical Guide for GTM Data](https://www.enrichments.io/blog/what-is-mcp-server): Learn what is an mcp server, how it connects AI clients to tools, and how GTM teams can design controlled enrichment workflows with clear access rules.
- [Direct Express Identity Verification Email: Safety Guide](https://www.enrichments.io/blog/direct-express-identity-email-safety): Learn how to assess a direct express identity verification email, spot warning signs, and use safe channels before sharing personal details.
- [Best B2B Data Enrichment Tools for CRM Accuracy Teams](https://www.enrichments.io/blog/b2b-enrichment-tools-crm-accuracy): Compare the best b2b data enrichment tools for crm accuracy using a practical framework for matching, field controls, validation, and workflow fit across your CRM.
- [Email Verification: A Workflow for Cleaner B2B Outreach](https://www.enrichments.io/blog/email-verification-b2b-outreach-workflow): Email verification helps GTM teams protect sender reputation and route reliable outreach. Learn how to interpret statuses and design a repeatable workflow.
- [Attio CRM AI Features for Data Enrichment Workflows](https://www.enrichments.io/blog/attio-crm-ai-data-enrichment): Attio CRM AI features for data enrichment work best with clear inputs and review rules. Learn a practical design for reliable CRM actions at scale.
- [Data Enrichment Services: A Buyer’s Operating Model](https://www.enrichments.io/blog/data-enrichment-services-buyer-guide): Data enrichment services can improve GTM records when ownership and controls are clear. Compare delivery models and choose a dependable workflow.
- [Data Enrichment CRM Best Practices for Trusted Routing](https://www.enrichments.io/blog/data-enrichment-crm-best-practices): Use data enrichment CRM best practices to set field rules, resolve conflicts, and keep routing and outreach based on trusted records across GTM.
- [HubSpot Data Enrichment: API and CSV Workflow Guide](https://www.enrichments.io/blog/hubspot-data-enrichment-api-csv): HubSpot data enrichment can add useful contact and company context through a governed API or CSV workflow without creating unmanaged fields.
- [Customer Data Enrichment: Build Trusted B2B Records](https://www.enrichments.io/blog/customer-data-enrichment-trusted-records): Customer data enrichment helps GTM teams resolve identities, add useful context, and keep records actionable without overwriting trusted data.
- [Email Verification API: Design Deliverability Checks](https://www.enrichments.io/blog/email-verification-api-design): Build an email verification api workflow that handles status outcomes, protects sending reputation, and keeps enrichment results actionable today.
- [Data Enrichment Tools: How to Evaluate Data Quality](https://www.enrichments.io/blog/data-enrichment-tools-evaluation): Compare data enrichment tools by coverage, field controls, validation, delivery options, and billing rules so your GTM team can choose with clarity.
- [B2B Data Enrichment: A Practical Guide for GTM Teams](https://www.enrichments.io/blog/b2b-data-enrichment-guide): Learn how b2b data enrichment adds usable contact and company context, when to enrich, and how to protect quality in GTM workflows.
- [Company Enrichment Data: Turn Domains Into GTM Context](https://www.enrichments.io/blog/company-enrichment-data-context): Company enrichment data turns a domain or company name into usable account context. Learn which fields to use, normalize, and maintain across your CRM.
- [Data Enrichment API: Build Reliable GTM Data Pipelines](https://www.enrichments.io/blog/data-enrichment-api-pipelines): A data enrichment API can resolve people and companies within your workflow. Learn how to design requests, validation, retries, and result handling.
- [CRM Data Enrichment: A Practical Guide to Cleaner Records](https://www.enrichments.io/blog/crm-data-enrichment-guide): CRM data enrichment helps teams complete records, standardize fields, and route accounts with confidence. Learn a practical workflow for cleaner CRM data.

## Optional

- [Security](https://www.enrichments.io/security): Controls that exist in the product today, and the ones we do not claim.
- [Privacy policy](https://www.enrichments.io/privacy): What is collected, why, and how to have it erased.
- [Terms of service](https://www.enrichments.io/terms): The contract.

Full version: https://www.enrichments.io/llms-full.txt