canonical: https://jentic.com/apis/interzoid.com/interzoid-get-company-name-match-similarity-key-api # Interzoid Get Company Name Match Similarity Key API Jentic publishes the only available OpenAPI specification for Interzoid Get Company Name Match Similarity Key API, keeping it validated and agent-ready. The API returns an algorithmic similarity key for a company name string so variants such as 'IBM', 'I.B.M.', and 'International Business Machines Corp' produce the same key, which lets deduplication and account-merging jobs join on the key instead of brittle string-equality logic. The single GET /getcompanymatch endpoint authenticates with a license key passed as a query parameter and returns the similarity key as JSON. ## For AI agents Generate a similarity key for a company name to deduplicate accounts and join lead lists. One GET endpoint, license-key auth. ## Scope Does not provide firmographic data, parent-subsidiary relationships, or canonical company name standardisation - use for fuzzy-match key generation on company name strings only. ## Capabilities - Generate a deterministic similarity key for a company or organization name - Collapse account records that store the same company under different legal-entity suffixes - Join two lead lists by hashing the company column to a similarity key first - Cluster opportunity records under a single account despite naming variations - Build match keys for company columns in MDM and account-deduplication pipelines ## Use cases ### Account-table deduplication in CRM Sales operations teams call the Interzoid Get Company Name Match Similarity Key API for every account name and group accounts that return the same key. Variants like 'IBM', 'IBM Corp', and 'International Business Machines' collapse to one cluster so reps no longer pursue the same prospect across multiple records. Example prompt: Iterate the accounts table, call /getcompanymatch with company set to each row's name, and group rows by the returned similarity key. ### Lead-list cross-reference When marketing imports a third-party lead list, exact-match joins on company name miss many overlaps with the existing CRM. Computing the Interzoid similarity key on both sides and joining on the key surfaces overlapping accounts so duplicate outreach is suppressed. Example prompt: Compute /getcompanymatch keys for the company column in both the inbound lead list and the existing CRM, then suppress leads whose key already exists in CRM. ### MDM company-name normalization layer Master data management pipelines call the Interzoid Get Company Name Match Similarity Key API on every customer record to attach a stable company cluster ID. Reporting layers aggregate revenue and pipeline by cluster ID rather than raw company string, eliminating duplicate-name distortion in dashboards. Example prompt: On every insert into the accounts staging table, call /getcompanymatch and persist the returned key as company_match_key for downstream BI. ### AI agent CRM cleanup An AI agent assisting a RevOps analyst discovers the Interzoid Get Company Name Match Similarity Key API through Jentic and uses it to flag near-duplicate accounts during a CRM hygiene sweep. Jentic stores the Interzoid license key in the credential vault and injects it as the license query parameter at execution time, so the agent never sees the raw key. Example prompt: Search Jentic for 'similarity key for company name', load the Interzoid Get Company Match operation, and execute it for each account name, then surface clusters of more than one account sharing a key. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/getcompanymatch` | Return a similarity key for a company name | ## Key resources - **Company match similarity key** — Single GET operation that accepts a company name and returns an algorithmic similarity key for fuzzy matching. ## Why Jentic - **Setup:** Wiring the Interzoid Get Company Name Match Similarity Key API by hand means registering for a license key, appending it as a license query parameter on every call to /getcompanymatch, and handling the HTTP plumbing yourself. Through Jentic you install once, import this API from the API Directory, store the license key once, and your agent calls it. - **Permission scoping:** This API exposes a single read-only GET /getcompanymatch operation that takes a company name string in the query, with no resource id in the URL path, so scoping is at the operation level: you limit the agent to the similarity-key lookup it needs and nothing else. Because it only generates a match key and writes nothing back, there is no destructive operation to include. - **Credential handling:** Your Interzoid license key is stored once, encrypted, by your own Jentic One instance and injected as the license parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'similarity key for a company name' or 'dedupe CRM accounts', and Jentic returns the Get Company Name Match operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Interzoid Get Company Name Match Similarity Key API** — Functionally equivalent slug variant for the same /getcompanymatch endpoint, sourced from APIs.guru - **Interzoid Get Full Name Match Similarity Key API** — Same similarity-key approach applied to person full-name fields; pair with company for B2B contact dedup - **Interzoid Get Address Match Similarity Key API** — Generates a similarity key for a full street address, useful as a tie-breaker when company names alone are ambiguous ## FAQ ### Why is there no official OpenAPI spec for Interzoid Get Company Name Match Similarity Key API? Interzoid does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Interzoid Get Company Name Match Similarity Key API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Interzoid Get Company Name Match Similarity Key API use? The API uses a license key passed as the license query parameter on every call to /getcompanymatch. Through Jentic the license key is held in the credential vault and injected at execution time, so the agent never handles the raw key. ### Can I match company names that include legal suffixes like 'Inc' or 'GmbH'? Yes. The similarity algorithm tolerates common legal-entity suffixes, so 'Acme Inc', 'Acme Corp', and 'Acme GmbH' typically collapse to a single key when the underlying name matches. ### What are the rate limits for the Interzoid Get Company Name Match Similarity Key API? The OpenAPI spec does not publish a numeric rate limit. Interzoid enforces per-license-tier quotas on the account dashboard, so check your account before running batch dedup jobs. ### How do I deduplicate company names through Jentic? Install the SDK with pip install jentic, search for 'similarity key for company name', load the Interzoid Get Company Match operation, and execute it for each company string, then group records by the returned key. ### Does the API distinguish between subsidiaries and parent companies? No. The /getcompanymatch endpoint produces a similarity key based on the literal company string. Subsidiary relationships are not part of the response and need a firmographic data source to resolve. ### Can I limit what my agent is allowed to do with the Interzoid Get Company Name Match Similarity Key API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes only the single read-only GET /getcompanymatch operation, so you scope the agent to just that similarity-key lookup and nothing else. There is no resource id in the URL path and the call writes nothing back, so scoping happens at the operation level with no destructive action to allow. You keep the agent limited to generating a match key from a company name string, while your license key stays with your instance and is injected at execution time rather than exposed to the agent.