What is a company enrichment API?
A company enrichment API takes a company identifier — usually a domain like acme.com — and returns structured firmographics: legal name, primary domain, HQ location, founded year, industry, LinkedIn URL, and headcount. Teams use it to fill and correct CRM records, qualify signups, segment accounts, and feed AI-agent workflows. Also called firmographic data APIs, company data enrichment tools, or B2B company data providers.
The hard part is not returning data — it's returning correctdata for the company you actually asked about. Subsidiaries get confused with parents, rebrands return stale identities, and long-tail international companies often don't resolve at all. That is what the independent benchmark measures.
What a company enrichment API returns
The benchmark normalizes every provider to one seven-field contract, judged against identity-verified LinkedIn reference data:
| Field | What it is (and where providers fail) |
|---|---|
| Legal name | The company's canonical name (rebrands are where providers fail) |
| Primary domain | The company's current website domain |
| HQ location | Headquarters country and city, judged as a pair |
| Founded year | Exact four-digit founding year |
| Industry | Judged with taxonomy synonyms accepted (SaaS ≈ software, etc.) |
| LinkedIn URL | The company's LinkedIn page — the identity anchor |
| Headcount band | Canonical LinkedIn employee band (11–50, 51–200, …) |
How to read enrichment accuracy numbers
“Accuracy” hides several different questions. The benchmark separates them:
| Metric | Definition |
|---|---|
| Correct field yield | Semantically correct returned fields ÷ all fields with available reference data. The headline: of the data you could have gotten right, how much did you get right? |
| Accuracy when present | Of the fields a provider returned, the share that were correct — measures how often wrong values get written to your CRM. |
| Attribute coverage | Share of the seven fields present in the response, regardless of correctness. |
| Resolution rate | Share of company domains that returned any response at all — long-tail and international companies are where this drops. |
| Median latency | Milliseconds per request — the constraint for real-time enrichment in product or agent flows. |
| Estimated cost | Recorded usage × each provider's public entry self-serve rate. Free allowances and volume discounts excluded. |
Returned ≠ right: a provider can fill every field (high coverage) and still write wrong values (low accuracy). That distinction is why the benchmark reports both.
There is no single “best” company enrichment API — the independent benchmark points to a different provider depending on the axis your workflow is constrained by. Every leader below is measured on 300 identity-verified companies:
- CRM data you can trust end to endPeople Data Labshighest correct field yield · 86.7%
- Few wrong values written — right when returnedPredictLeadshighest accuracy when present · 88.7%
- Fill the most fields per companyFiberhighest attribute coverage · 97.2%
- Long-tail / international companies must resolveOcean.iohighest resolution rate · 100.0%
- Real-time enrichment in product or agent flowsPeople Data Labslowest median latency · 274 ms
- Budget-constrained backfillsOcean.iolowest estimated cost · $1.92 cohort
Full leaderboard, methodology, and per-company evidence: the company enrichment benchmark →
Company enrichment — common questions
What is a company enrichment API?
An API that takes a company identifier (usually a domain) and returns structured firmographic data about that company — name, primary domain, HQ location, founded year, industry, LinkedIn URL, and headcount. Teams use it to fill and correct CRM records, qualify signups, segment accounts, and feed agent workflows. Company enrichment APIs are also called firmographic data APIs, company data enrichment tools, or B2B company data providers.
What is the difference between company enrichment and lead or contact enrichment?
Company (firmographic) enrichment describes the organization — industry, size, location. Lead/contact enrichment describes a person — email, title, phone. Many vendors sell both, but they are different datasets with different accuracy characteristics. The benchmark on this site measures company-level enrichment only; treat contact-level accuracy as a vendor claim until measured.
How accurate are company enrichment APIs?
Measured on 300 identity-verified companies: correct field yield ranges across providers, with People Data Labs currently leading at 86.7% — meaning even the best provider gets a meaningful share of available fields wrong or missing. Subsidiaries and recent rebrands are the hardest cases. The full per-provider and per-company breakdown is on the benchmark.
How should I evaluate a company enrichment provider?
Don't trust demo accuracy on famous companies — every provider resolves Google. Test on your actual traffic shape: long-tail domains, international companies, subsidiaries, and rebrands. Measure correct field yield (not just coverage — returned ≠ right), check resolution rate on obscure domains, and compare cost at your real volume. Or start from an independent benchmark that already did this on identical inputs.