Skip to main content
The agent uses the maintained company-to-info Play, backed by People Data Labs, to look up company profiles. It matches each entity before accepting its profile or business fields. Provide names or websites with stable source IDs, requested fields, and whether you mean the operating company, parent, or subsidiary. For CRM proposals, include existing account IDs, values, and any segment threshold.

Check the entity before its fields

Preserve original website values while separating the hostname from paths and tracking parameters. Meaningful subdomains can identify different entities; a personal mailbox domain does not establish an employer. For a company profile URL, compare its associated website and organizational context with your target. If the lookup has no URL, the agent can search the company name and domain together and check candidate profiles. A guessed slug or similarly named search result is not a confirmed match. Each proposed field needs its previous and candidate value, source, observation time, and acceptance reason. Missing values stay unknown, and provider errors stay distinct from no match. The agent prepares proposals; CRM updates need the CRM repair workflow.
A fictional Example Labs profile can match while its 51–200 employee range crosses your 100-employee segment threshold. Accept the profile, retain the range and source date, leave exact headcount unknown, and hold the segment. Neither the midpoint nor a parent’s 1,400 employees resolves that uncertainty. Preserve the existing account owner.
For a file, include parent/subsidiary, rebrand, consumer-domain, and no-match cases. CSV input and saved-run results cover file preparation and export. Review and operate a workflow covers authorization, pilots, and recovery. Agent guide: CLI and SDK instructions →