canonical: https://jentic.com/apis/interzoid.com/interzoid-get-country-match-similarity-key-api

# Interzoid Get Country Match Similarity Key API

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.

## For AI agents

Generate a similarity key for a country name to deduplicate or fuzzy-match country columns across datasets. One GET endpoint, license-key auth.

## Scope

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.

## Capabilities

- 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
- Build match keys for country columns in MDM and reporting pipelines

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/getcountrymatch` | Return a similarity key for a country name |

## Key resources

- **Country match similarity key** — Single GET operation that accepts a country name and returns an algorithmic similarity key for fuzzy matching.

## Why Jentic

- **Setup:** Wiring the Interzoid Get Country Match Similarity Key API by hand means obtaining a license key, appending it as a license query parameter on each call to /getcountrymatch, and handling the request 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 /getcountrymatch operation that takes a country 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. It only computes a match key and writes nothing, so 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 country name' or 'match inconsistent country strings', and Jentic returns the Get Country Match operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Interzoid Get City Match Similarity Key API** — Same similarity-key approach applied to city names; pair with country for full address fuzzy matching
- **Interzoid Get Address Match Similarity Key API** — Operates on full street addresses rather than country names alone
- **Interzoid State Data Standardization API** — Standardises US state values to a canonical form, useful alongside country fuzzy matching for address dedup

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Interzoid Get Country 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 a single read-only GET /getcountrymatch operation, so you scope the agent at the operation level to just the similarity-key lookup it needs. That call takes a country name string in the query and has no resource id in the URL path, and it only computes a match key while writing nothing, so there is no destructive operation to grant. You keep the agent restricted to this one country-match lookup and withhold every other operation and credential.