Interzoid Get City Match Similarity Key API

Name: Interzoid Get City Match Similarity Key API API
Brand: Interzoid Get City Match Similarity Key API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey1 EndpointsREST

For Agents

Connect the Interzoid Get City Match Similarity Key API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Get City 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

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

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

Capabilities

What an agent can do with Interzoid Get City Match Similarity Key API API.

Generate a deterministic similarity key for a city name string

Deduplicate customer records that hold the same city under different spellings

Join two datasets on city by hashing each side to a similarity key first

Cluster ticketing or order records by metropolitan area despite formatting variations

GET STARTED

Start building with Interzoid Get City Match Similarity Key API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Interzoid Get City Match Similarity Key API, keeping it validated and agent-ready.

The Interzoid Get City Match Similarity Key API returns an algorithmic similarity key for a given city name string. Two records that refer to the same city — even when spelled inconsistently as 'NYC', 'New York', or 'New York City' — produce the same key, so deduplication and fuzzy-matching jobs can join on the key instead of the raw text. The single GET /getcitymatch endpoint authenticates with a license key passed as a query parameter and returns the similarity key as JSON.

Use Cases

Patterns agents use Interzoid Get City Match Similarity Key API API for, with concrete tasks.

★ Customer table deduplication on city

Data engineers run every row's city value through the Interzoid Get City Match Similarity Key API and group records by the returned key to find duplicates. Records spelled 'NYC', 'New York', and 'New York City' collapse to the same key, surfacing duplicates that exact-match logic would miss. The endpoint accepts one city per call so batches use a thread pool sized to the account rate limit.

Iterate the customers table, call /getcitymatch with city set to each row's city value, and group rows by the returned similarity key.

Cross-dataset join on city

When merging a CRM export with a marketing list, exact joins on city fail because the two systems format city names differently. By computing the Interzoid similarity key for both sides and joining on the key, the merge captures matches the literal string compare misses, without writing custom regex or stemming code.

Compute /getcitymatch keys for the city column in both CRM and marketing exports, then join on the key to produce a unified contact view.

MDM city standardisation pipeline

Master data management pipelines call the Interzoid Get City Match Similarity Key API to assign each incoming customer record a stable city cluster ID. Variants flow into the same cluster automatically, and downstream BI dashboards aggregate by cluster ID rather than by raw text, producing accurate per-city counts.

On every insert into the customers staging table, call /getcitymatch and store the returned key as city_match_key for downstream aggregation.

AI agent record-deduplication assistant

An AI agent helping an analyst clean a contact list discovers the Interzoid Get City Match Similarity Key API through Jentic and uses it to flag rows that look like the same city under different spellings. 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 city name', load the Interzoid Get City Match operation, and execute it for each unique city string in the contacts file.

Key Endpoints

1 endpoints — the interzoid get city match similarity key api returns an algorithmic similarity key for a given city name string.

METHOD

PATH

DESCRIPTION

GET

/getcitymatch

Return a similarity key for a city name

GET

/getcitymatch

Return a similarity key for a city name

Why though Jentic?

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 /getcitymatch, so the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'similarity key for city name' or 'fuzzy match cities'. Jentic returns the Interzoid Get City 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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Interzoid City Data Standardization API

Standardises a city name to a canonical form rather than producing a similarity key

Choose this when you want a clean canonical city string in your records, not just a join key.

Complementary

Interzoid Get Country Match Similarity Key API

Same similarity-key approach applied to country names; pair with city for full address fuzzy matching

Use alongside the city match API when you need to fuzzy-match both city and country fields in the same records.

Alternative

Interzoid Get Address Match Similarity Key API

Operates on a full street address rather than a city alone, returning a similarity key for the whole address

Choose this when your dedup unit is a full street address, not just a city.

FAQs

Specific to using Interzoid Get City Match Similarity Key API API through Jentic.

What authentication does the Interzoid Get City Match Similarity Key API use?

The API uses a license key passed as the license query parameter on every call to /getcitymatch. 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 cities that include the state or country in the same field?

The /getcitymatch endpoint takes a single city string. It is most reliable when state and country are stripped first; if your records combine them, parse the components and call this API for the city portion only.

What are the rate limits for the Interzoid Get City 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 deduplication jobs.

How do I deduplicate a city column through Jentic?

Install the SDK with pip install jentic, search for 'similarity key for city name', load the Interzoid Get City Match operation, and execute it for each city in your dataset, then group rows by the returned key.

Does the API match cities across languages or transliterations?

The similarity algorithm targets common English-language variations and typos. For non-Latin scripts or significant transliteration differences, normalize the input before calling /getcitymatch for best results.