Skip to main content
A coding agent can find every Explorium API call, MCP server entry, and stored Explorium value in your codebase, rewrite the calls to the official CompanyEnrich SDK, and list what has no equivalent. 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 filter tables. The instructions work in any language and cover AgentSource v1 and v2.
Explorium says AgentSource will be discontinued on December 2, 2026. Unlike a gradual migration, every call site needs a CompanyEnrich path, another provider, or removal. The report lists which is which.

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 Explorium 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 Explorium working until you switch. The Explorium path stays behind the flag until you remove it.
  • Not guess. Any field, input, or filter without an entry in the mapping file gets a TODO and a line in the report.
  • 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, the filters the agent marked for redesign, and the features with no equivalent.

Instructions

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

Limitations

  • The mapping covers AgentSource v1 and v2 as documented on November 16, 2026. Check the checkedAt date in the mapping file.
  • The agent cannot decide whether a lossy field is good enough for your product, or what replaces a feature with no equivalent. The report lists both 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 and MCP tool mapping, request and response differences, and the parity check.

Field mapping

The human-readable version of the mapping file.

Search filters

How Explorium fetch filters become CompanyEnrich filters.

MCP server

Connect your AI client to CompanyEnrich.