Skip to main content
A coding agent can find every People Data Labs (PDL) call in your codebase, rewrite the ones CompanyEnrich supports to the official SDK, and leave the rest in place with a note. This page holds the instructions it follows. The agent reads them together with the mapping file, the same data behind the field mapping and search query tables. The instructions work in any language, not only Python, and the agent writes native SDK calls rather than a compatibility layer.

Start the migration

Open your agent in the repository and give it this prompt:
The URL ends in .md, which serves this page as plain Markdown for the agent to read. If your agent cannot open URLs, download the mapping file and the API specification into the repository, and paste the instructions into the agent’s instruction file, such as AGENTS.md, CLAUDE.md, or a Cursor rule. Then tell it where the files are and ask it to follow the instructions.

What the agent does

Guardrails

The instructions tell the agent to:
  • Stop for review. No code changes before you approve the report.
  • Spend nothing. No paid CompanyEnrich requests and no PDL requests. Tests use mocked HTTP. With your key, the agent may call only free endpoints: GET /v2/me, the counts, and the lookups for filter values.
  • Keep PDL working. The PDL path stays behind the flag until you remove it.
  • Not guess. Any field, input, or query without an entry in the mapping file stays on PDL with a TODO.
  • Protect keys. Keys come from environment variables and are never printed or committed.
Review the diff as you would any other change. Pay most attention to the lossy fields your code depends on and to the queries the agent marked for redesign.

Instructions

Copy this block if you want to keep the instructions in your repository.

Limitations

  • The mapping covers PDL v5 as documented on November 13, 2026. Check the checkedAt date in the mapping file.
  • The agent cannot decide whether a lossy field is good enough for your product. The report lists those fields for you.
  • Search translations change results by design, because the two APIs rank and match differently. Compare totals with the free count endpoints before you switch.

Migration overview

Endpoint mapping, request and response differences, and the parity check.

Field mapping

The human-readable version of the mapping file.

Search queries

How PDL queries become filters.

MCP server

Give agents live access to CompanyEnrich data.