Entity resolution

Resolve a name, a URL, or a stray string to the apex domain the record keys on, so the rest of your pipeline has something stable to join against.

Request access

Domain-first by design: the key is the thing that stays put.

The job

The join key is the hard part.

Your CRM has the trading name, the contract has the legal entity, the support ticket has a subdomain, and the invoice has an abbreviation. Each is the same customer, and none of them match on a string compare, so the same company is counted three times in every report built on top.

Bixel keys everything on the apex domain, which survives rebrands and marketing names better than any label does, and resolves inbound names to it. Downstream, one company is one row.

What that costs today

  • The same customer counted three ways in one report
  • Fuzzy matching that quietly merges two real companies
  • Renames that orphan a year of history
  • Subdomains treated as separate businesses

The API

3 calls cover the job.

Current state is open. History values, claim checks, and evidence trails sit behind a free key. These are the real routes.

GETopen
/v1/search

Name to canonical domain; the resolver front door.

GETopen
/v1/companies/{company}

The resolved record, keyed on apex domain.

GETopen
/v1/categories/{slug}

A resolved roster, for reconciling a list in bulk.

For agents · MCP

Or let your agent run it.

Connect the Bixel MCP server and any agent, Claude, an internal copilot, a procurement bot, works this job against live structured data, with every value citing the dated capture it came from. The recommendation becomes auditable, not a guess.

See the MCP tool list

You ask your agent

“Here are 200 company names from our CRM. Resolve each to its domain and tell me which ones you could not.”

One company, however it was written down.

Every company in a category resolves to one domain-keyed record: see a resolved roster →

More in AI & Agents

The answer layer for agents that need company facts with receipts.