For Agents
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Get Company Name Match Similarity Key API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Interzoid Get Company Name Match Similarity Key API API.
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
GET STARTED
Generate a similarity key for a company name to deduplicate accounts and join lead lists. One GET endpoint, license-key auth.
Use for: Generate a similarity key for 'International Business Machines', Deduplicate the accounts table on company name, Match 'IBM Corp' and 'International Business Machines' as the same company, Get a fuzzy match key for a company name
Not supported: Does not provide firmographic data, parent-subsidiary relationships, or canonical company name standardisation — use for fuzzy-match key generation on company name strings only.
Jentic publishes the only available OpenAPI document for Interzoid Get Company Name Match Similarity Key API, keeping it validated and agent-ready.
The Interzoid Get Company Name Match Similarity Key API returns an algorithmic similarity key for a company name string. Variants such as 'IBM', 'I.B.M.', and 'International Business Machines Corp' produce the same key, so deduplication and account-merging jobs can 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.
Build match keys for company columns in MDM and account-deduplication pipelines
Patterns agents use Interzoid Get Company Name Match Similarity Key API API for, with concrete tasks.
★ 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.
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.
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.
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.
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.
1 endpoints — the interzoid get company name match similarity key api returns an algorithmic similarity key for a company name string.
METHOD
PATH
DESCRIPTION
/getcompanymatch
Return a similarity key for a company name
/getcompanymatch
Return a similarity key for a company name
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Interzoid license key is stored encrypted in the Jentic vault and injected as the license query parameter on each call to /getcompanymatch, so the raw key never enters the agent's context.
Intent-based discovery
Agents search Jentic with intents like 'similarity key for company name' or 'dedup CRM accounts'. Jentic returns the Interzoid Get Company Match operation with its parameter schema for direct execution.
Time to first call
Direct Interzoid integration: 1-2 hours including license registration and HTTP wiring. Through Jentic: a few minutes via search, load, and execute.
Alternatives and complements available in the Jentic catalogue.
Interzoid Get Company Name Match Similarity Key API
Functionally equivalent slug variant for the same /getcompanymatch endpoint
Choose between the two slug variants based on which one is wired into your existing tooling — both call the same operation.
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
Use alongside the company match API when both contact name and company need to be fuzzy-matched in the same dedup pass.
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
Use when company name alone is not enough to disambiguate accounts and address is also captured.
Specific to using Interzoid Get Company Name Match Similarity Key API API through Jentic.
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.