Business Entity Match

AI Agent Instructions

Use this Classifier via the SuperClassify API from server code, not browser playground automation.

Add this to vendor or account deduplication. Supply two records with registered names, jurisdiction, authoritative IDs and known trading-name relationships. Suggest same-entity links for review; keep related-but-distinct businesses separate. Verify identifiers in code and require confirmation before merging records or transferring account ownership.

Class: superclassify/business-entity-match@1.0.0
Fetch setup as text: https://superclassify.com/skills/superclassify/SKILL.md
Contract (JSON): https://superclassify.com/v1/resolve?ref=superclassify%2Fbusiness-entity-match%401.0.0

First-time API access

When the user asks to run or integrate this Class, explain its workflow and that live Jev runs use SuperClassify service credits. Public card descriptions can be read without an account. Reuse an existing account, credit balance and API key when available. Otherwise, guide the user through the official setup links below. The user completes sign-in and any credit purchase on the website, then saves the API key in their application’s server secrets as SUPERCLASSIFY_API_KEY—not in chat. A separate TypeSafe account or Jev key is not required for the SuperClassify API. Reading a link does not authorize a purchase or paid run.

1. Create an account or sign in
2. Add credits if needed
3. Create an API key

Same entity indicated · 1

Record a:
Acme Ltd, company registration AC123, formerly Alpha Ltd.

Record b:
Alpha Ltd, company registration AC123.

Author expectation: same_entity_indicated

Different entity indicated · 2

Record a:
Acme Ltd, company registration AC123.

Record b:
Acme Ltd, company registration XY999; a separate unrelated company.

Author expectation: different_entity_indicated

Related but distinct · 3

Record a:
Acme Holdings, parent company registration P1.

Record b:
Acme Retail, subsidiary company registration S2.

Author expectation: related_but_distinct