For Agents
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Get Country 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 Country Match Similarity Key API API.
Generate a deterministic similarity key for a country name string
Collapse country aliases like 'USA', 'United States', and 'America' into a single key
Join two datasets on country by hashing each side to a similarity key first
Cluster customer records by country despite formatting variations
GET STARTED
Generate a similarity key for a country name to deduplicate or fuzzy-match country columns across datasets. One GET endpoint, license-key auth.
Use for: Generate a similarity key for the country 'United States of America', Match 'USA' and 'United States' as the same country, Deduplicate a customer table on country, Get a fuzzy match key for a country name
Not supported: Does not return ISO country codes, geocode locations, or standardise country names to a canonical form — use for fuzzy-match key generation on country name strings only.
Jentic publishes the only available OpenAPI document for Interzoid Get Country Match Similarity Key API, keeping it validated and agent-ready.
The Interzoid Get Country Match Similarity Key API returns an algorithmic similarity key for a country name string. Variants like 'United States', 'USA', 'U.S.A.', and 'America' produce the same key, so deduplication and dataset-merge jobs can join on the key instead of maintaining a country-alias lookup table. The single GET /getcountrymatch endpoint authenticates with a license key passed as a query parameter and returns the similarity key as JSON.
Build match keys for country columns in MDM and reporting pipelines
Patterns agents use Interzoid Get Country Match Similarity Key API API for, with concrete tasks.
★ Country-column deduplication
Data engineers run every record's country value through the Interzoid Get Country Match Similarity Key API and group records by the returned key to consolidate aliases. 'USA', 'United States', and 'United States of America' collapse to one cluster, producing accurate per-country totals in dashboards.
Iterate the customers table, call /getcountrymatch with country set to each row's value, and group rows by the returned key.
Cross-dataset country merge
Two systems often store country names differently — one as ISO names, another as informal aliases. Computing the Interzoid similarity key on both sides lets the merge join on the key and capture matches that exact-string compare would miss.
Compute /getcountrymatch keys for the country column in two exports and join on the key to produce a unified view.
Reporting normalization for global revenue
BI dashboards aggregating revenue by country mis-count when 'UK', 'United Kingdom', and 'Britain' appear as separate rows. Storing the Interzoid similarity key alongside the raw value lets aggregations group by the key, producing one accurate row per country.
On insert into the orders staging table, call /getcountrymatch and store the returned key as country_match_key for downstream BI grouping.
AI agent dataset reconciliation
An AI agent reconciling two customer datasets discovers the Interzoid Get Country Match Similarity Key API through Jentic and uses it to align country columns before merging. 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 country name', load the Interzoid Get Country Match operation, and execute it for each unique country string in both datasets.
1 endpoints — the interzoid get country match similarity key api returns an algorithmic similarity key for a country name string.
METHOD
PATH
DESCRIPTION
/getcountrymatch
Return a similarity key for a country name
/getcountrymatch
Return a similarity key for a country 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 /getcountrymatch, so the raw key never enters the agent's context.
Intent-based discovery
Agents search Jentic with intents like 'similarity key for country name'. Jentic returns the Interzoid Get Country 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 City Match Similarity Key API
Same similarity-key approach applied to city names; pair with country for full address fuzzy matching
Use alongside the country match API when both city and country fields need fuzzy joining.
Interzoid Get Address Match Similarity Key API
Operates on full street addresses rather than country names alone
Choose this when your dedup unit is a complete address, not just the country component.
Interzoid State Data Standardization API
Standardises US state values to a canonical form, useful alongside country fuzzy matching for address dedup
Use when records include US states that also need normalization in the same pipeline.
Specific to using Interzoid Get Country Match Similarity Key API API through Jentic.
What authentication does the Interzoid Get Country Match Similarity Key API use?
The API uses a license key passed as the license query parameter on every call to /getcountrymatch. Through Jentic the license key is held in the credential vault and injected at execution time, so the agent never handles the raw key.
Does the Interzoid Get Country Match Similarity Key API match ISO country codes?
The endpoint operates on country name strings rather than ISO codes. If your data contains ISO 3166 codes, expand them to country names before calling /getcountrymatch, or use a code-to-name lookup as a preprocessing step.
What are the rate limits for the Interzoid Get Country 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 jobs.
How do I deduplicate a country column through Jentic?
Install the SDK with pip install jentic, search for 'similarity key for country name', load the Interzoid Get Country Match operation, and execute it for each country string, then group rows by the returned key.
Does the API match country names in non-English languages?
The similarity algorithm targets common English-language variations and aliases. For names in other languages or non-Latin scripts, normalize to an English equivalent before calling /getcountrymatch for best results.