canonical: https://jentic.com/apis/companyenrich.com/companyenrich

# Company Enrich API v2

The Company Enrich API returns firmographic profiles for companies looked up by domain or by identifying properties, and enriches people records from an email address. It searches and counts companies and people with structured filters, natural-language semantic queries, and lookalike matching against seed domains. Batch and asynchronous bulk enrichment jobs, search exports, and reference lookups for industries, technologies, keywords, job positions, and geography round out the surface.

## For AI agents

Enrich a company by domain, find lookalike companies, search people by seniority or department, and look up a person's work email through the Company Enrich API.

## Scope

Does not send outreach emails, manage CRM records, or verify email deliverability. Use for company and people data enrichment and search only.

## Capabilities

- Enrich a company profile from its domain, or from identifying properties when the domain is unknown
- Search and count companies with structured filters, a semantic natural-language query, or lookalike seed domains
- Search people by position, seniority, department, location, education, and company, with cursor pagination
- Identify a person from an email address and find a person's work email by person id
- Run batch and asynchronous bulk enrichment of company domains, then download the results file
- Export company and people search results asynchronously for offline processing
- Look up reference values for industries, technologies, keywords, job positions, countries, states, and cities

## Use cases

### AI agent account research

A sales-research agent given a list of prospect websites needs firmographics before writing outreach. Through Jentic it searches for 'enrich a company by domain', loads the Company Enrich operation with its input schema, and calls it with each domain while the bearer token is injected at call time. The agent gets back a structured company profile it can summarise, without the developer hand-wiring the HTTP client.

Example prompt: Call GET `/v2/companies/enrich` with domain=stripe.com and summarise the returned company profile in three bullet points

### Lookalike prospect list building

Growth teams that already know their best customers want more companies like them. The Company Enrich search accepts a lookalike block of seed domains or a semantic natural-language query alongside structured filters, and the count and preview operations size the result before paging through it. This turns a handful of known accounts into a filtered prospect list.

Example prompt: POST `/v2/companies/search/count` with a lookalike block of three seed domains, then POST `/v2/companies/search` with pageSize 25 and return the company names

### Contact discovery for outreach

After picking target accounts, a rep needs the right people and a way to reach them. People search filters by position, seniority, department, location, and company, and the work-email lookup returns an address for a chosen person id, optionally hinted with the company domain. Email-based enrichment works in the other direction, identifying the person behind an inbound address.

Example prompt: POST `/v2/people/search` filtered to the sales department at one company, then call GET `/v2/people/{personId}/email` for the top result

### Bulk CRM backfill

A CRM with thousands of account domains and missing firmographics needs a one-off backfill. POST `/v2/companies/enrich/batch` takes a domains array for synchronous batches, while POST `/v2/companies/enrich/bulk` starts an asynchronous job whose results file is downloaded once complete. Batch status and cancel operations let a script watch progress and stop leftover requests.

Example prompt: Start POST `/v2/companies/enrich/bulk` with a list of domains, poll GET `/v2/batches/{id}` until complete, then download the results

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/companies/enrich` | Enrich a company by domain |
| POST | `/v2/companies/search` | Search companies |
| POST | `/v2/people/search` | Search people |
| POST | `/v2/people/enrich` | Enrich a person by email |
| GET | `/v2/people/{personId}/email` | Find a person's work email |
| POST | `/v2/companies/enrich/bulk` | Enrich company domains asynchronously |
| GET | `/v2/batches/{id}` | Get batch status |

## Key resources

- **Companies** — Enrich by domain or properties, get by id, autocomplete, workforce insights, search, count, preview, and export
- **People** — Get by id, enrich by email, find work email, search, count, preview, and export
- **Batches** — List batches, check status, cancel remaining requests, and download raw results
- **Reference data** — Industries, keywords, technologies, positions, regions, countries, states, and cities

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/companyenrich.com/companyenrich/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Company Enrich by hand means attaching a bearer token to every call, handling cursor pagination on search, and polling asynchronous bulk and export jobs for their results. Through Jentic you install once, import Company Enrich from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Company Enrich carries search filters and target domains in query strings and request bodies, so rules bound which operations your agent may call rather than which companies it looks up. You choose the operations it may call, so credit-heavy ones like bulk enrichment or search exports are not included unless you add them.
- **Credential handling:** Your Company Enrich token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'enrich a company by domain' or 'find similar companies', and Jentic returns the matching Company Enrich operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Apollo.io** — Sales intelligence platform with people and company search plus sequencing
- **People Data Labs** — Person and company enrichment datasets with query-based search
- **Clearbit** — Company and person enrichment by domain and email
- **HubSpot CRM Companies** — CRM company records that enriched firmographics can be written back into

## FAQ

### What authentication does the Company Enrich API use?

Per its OpenAPI spec, the Company Enrich API authenticates every operation with a bearer token sent in the Authorization header as `Authorization: Bearer {token}`. Through Jentic the token is held by your own instance and attached at call time, so it never appears in the agent's context.

### Can I find companies similar to my existing customers with the Company Enrich API?

Yes. POST `/v2/companies/search` accepts a lookalike block of seed company domains and a semantic natural-language query alongside structured filters. Use POST `/v2/companies/search/count` or `/v2/companies/search/preview` first to size the result, then page through with the cursor.

### What are the rate limits for the Company Enrich API?

The OpenAPI spec does not specify rate limits. Check the Company Enrich documentation at https://docs.companyenrich.com for current limits and credit usage before running large batch or bulk jobs.

### Is there a Company Enrich MCP server?

You don't need an MCP server to give your agent Company Enrich. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the enrichment and search operations it needs, discovered on demand rather than loaded as a block of tool definitions.

### How do I enrich a company by domain through Jentic?

Search Jentic for 'enrich a company by domain', load the GET `/v2/companies/enrich` operation, and execute it with the required domain query parameter. Set waitForEnrichment if you want the call to wait for fresh data. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Company Enrich API?

Yes. For a research agent, write a rule that allows GET `/v2/companies/enrich` and POST `/v2/companies/search`, and the agent can look up and search companies while bulk jobs, exports, and work-email lookups stay off its list. Every call it makes is logged.
