canonical: https://jentic.com/apis/interzoid.com/interzoid-city-data-standardization-api

# Interzoid City Data Standardization API

Jentic publishes the only available OpenAPI specification for the Interzoid City Data Standardization API, keeping it validated and agent-ready. The single endpoint takes a city name (US or international) and returns a pre-selected standardised version of that city, intended to fix common variant spellings, casing, and abbreviations before deduplication, joining, or analytics. Authentication is an Interzoid license key passed as the 'license' query parameter alongside the city to standardise.

## For AI agents

Standardise a free-text city name into Interzoid's canonical form ahead of deduplication, joins, or analytics.

## Scope

Does not handle geocoding, postal validation, full address parsing, or country-name standardisation - use for canonicalising US and international city-name strings only.

## Capabilities

- Convert variant city-name spellings into Interzoid's canonical standardised form
- Cover both US and international cities through the same endpoint
- Return a result code and remaining-credit count alongside the standardised city
- Authenticate with an Interzoid license key passed as a query parameter

## Use cases

### CRM Deduplication Pre-Processing

Data teams standardise the city field across CRM records before deduplication so that variants like 'St. Louis', 'Saint Louis', and 'St Louis' collapse into one canonical key. The API returns the standardised city name in a single GET call per record. Match rates on subsequent dedupe passes rise materially compared with raw-string matching.

Example prompt: Call GET /getcitystandard with city='St. Louis' and return the CityStandard value to use as the merge key

### Analytics ETL Cleanup

Analytics pipelines normalise city dimensions before loading into a warehouse so that dashboards group consistently. Calling /getcitystandard during the transform step replaces a hand-maintained synonym table with a maintained service. The result includes a remaining-credit indicator so the pipeline can alert before the licence runs out.

Example prompt: Standardise the city values in a 50,000-row customer table by calling GET /getcitystandard for each unique input and caching the result

### Form-Submission Canonicalisation

Web forms collect free-text city values from users; canonicalising at submission time avoids dirty data ever reaching the database. A small server-side hook calls /getcitystandard, stores the standardised name, and keeps the original for audit. The end-to-end change is a few lines of code per form.

Example prompt: On form submit, call GET /getcitystandard with the user-entered city and persist both the original and standardised values

### Agent-Driven Data Enrichment

An AI agent enriching a customer record asks Jentic for 'standardise a city name', receives the Interzoid operation schema, and returns the canonical form alongside the original. Jentic stores the Interzoid licence key in your Jentic One instance and injects it as the query parameter at execution time, so the agent never sees the raw key. Enrichment that previously required a custom integration becomes a one-shot agent capability.

Example prompt: Given a customer record with city='SF', call /getcitystandard and update the record with the canonical CityStandard value

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/getcitystandard` | Return the standardised city name for a given input |

## Key resources

- **City Standardization** — Single GET endpoint that returns the canonical form of a US or international city name

## Why Jentic

- **Setup:** Wiring the Interzoid City Data Standardization API by hand means passing your licence key as a query parameter on every call and remembering the single /getcitystandard endpoint. Through Jentic you install once, import the Interzoid City Data Standardization API from the API Directory, store the licence key once, and your agent calls it.
- **Permission scoping:** This API exposes one read-only operation, GET /getcitystandard, with the city string in the query, so limit the agent to that operation. It performs no writes or deletes, so there is nothing destructive to add.
- **Credential handling:** Your Interzoid licence key is stored once, encrypted, by your own Jentic One instance and injected as the license query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'standardise a city name', and Jentic returns the GET /getcitystandard operation with its city query parameter so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Interzoid State Data Standardization API** — Companion endpoint that standardises US state names alongside the city standardiser
- **Interzoid Get Address Match Similarity Key API** — Generates a similarity key for full street addresses where the city standardiser handles the city component
- **Abstract API Geolocation** — Geolocation and IP-based location data versus Interzoid's pure name-standardisation focus

## FAQ

### Why is there no official OpenAPI spec for the Interzoid City Data Standardization API?

Interzoid does not publish OpenAPI specifications for its endpoints. Jentic generates and maintains this spec so that AI agents and developers can call the Interzoid City Data Standardization 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 City Data Standardization API use?

Authentication is a license key passed as the 'license' query parameter on the GET /getcitystandard request. Register at www.interzoid.com/register to obtain a key. Through Jentic, the key is stored in your Jentic One instance and injected into the query string at execution time so it never enters the agent's prompt.

### Can the API handle international city names?

Yes. The endpoint handles both US and international cities through the same /getcitystandard call - the input is a free-text city string regardless of locale. The standardised output reflects Interzoid's canonical form for that city.

### What are the rate limits for the Interzoid City Data Standardization API?

Interzoid runs on a credit-per-call model rather than a hard rate limit. Each successful response includes a 'Credits' field showing the remaining balance, and HTTP 402 is returned when credits are exhausted. The license tier purchased determines the credit pool.

### How do I standardise a city through Jentic?

Search Jentic for 'standardise a city name'. The SDK returns the GET /getcitystandard operation with the city query parameter. Run pip install jentic, await client.search('standardise a city name'), then await client.execute(...) with the city value.

### Is the Interzoid City Data Standardization API free?

Interzoid offers a free tier with limited credits to register and test, then paid tiers measured in API credits. See www.interzoid.com for current pricing. The 'Credits' field on each response shows the remaining balance for the calling licence.

### Can I limit what my agent is allowed to do with the Interzoid City Data Standardization API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use, and this API exposes only one read-only operation, GET /getcitystandard, so you can restrict the agent to that single call. It performs no writes or deletes, meaning there is nothing destructive to expose in the first place. Your Interzoid license key stays in your own Jentic One instance and is injected as the license query parameter at execution time, so the agent never handles the raw key.