> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Enrich Company

> Run company-to-info and distinguish a company match from nullable enrichment fields.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/task-enrich-company.md)

Enrich one company and inspect which fields the selected Play actually found.
This task ends with a reviewed company profile, not an automatic CRM update.

## Before you start

Use a company domain or name. Preserve the original identifier alongside the
result. A similar company name does not establish the same business entity.

The maintained `company-to-info` Play uses People Data Labs company enrichment.
It does not automatically merge three providers or promise every field will
be populated. Its typed result contains nullable fields and explicit misses.

## 1. Inspect the Play

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline describe prebuilt/company-to-info --json
deepline plays check prebuilt/company-to-info
```

Read the current input, output, access, and pricing information. Checking the
Play does not run enrichment.

## 2. Query one known company

Use a domain you are authorized to research. This example starts provider work:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline plays run prebuilt/company-to-info \
  --input '{"domain":"stripe.com"}' \
  --watch
```

Save the returned run ID. Inspect the same run:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline runs get <run-id> --full --json
```

## 3. Separate identity from field availability

Check `company_found` and `miss_reason` first. Compare `company_name` and
`company_domain` with the intended company.

Then inspect the required business fields. Examples include `headcount`,
`industry`, `hq_country`, and `total_funding_usd`. A null field is missing
evidence. It is not automatically zero or an empty business fact.

> [!TIP]
>
> Keep the result only when its identity fits your input. Preserve null fields
> and miss reasons instead of filling unsupported values.

If you need several sources, author their selection and precedence rules in a
[custom Play](https://deepline.com/docs/sdk-v2/plays.md). Do not assume that a natural-language request
changes the maintained Play's implementation.

## 4. Expand to a file after review

Inspect `prebuilt/company-to-info-batch`. Map its actual CSV input contract,
then use [Batch CSV enrichment](https://deepline.com/docs/sdk-v2/batch-csv.md) for a representative pilot.
Keep company identity and unknown fields in the export.

Ask your agent to explain an identity mismatch before replacing your CRM data.
See [account enrichment](https://deepline.com/docs/guides/account-enrichment.md) for a field-level workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.