Install Jentic One Beta

Connect the Interzoid City Data Standardization API to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finterzoid.com%2Finterzoid-city-data-standardization-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finterzoid.com%2Finterzoid-city-data-standardization-api" | 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 City Data Standardization API.

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

Patterns agents use Interzoid City Data Standardization API for, with concrete tasks.

GET STARTED

Start building with Interzoid City Data Standardization API

Explore with Jentic One

View OpenAPI Document

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

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.

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.

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.

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

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for the interzoid city data standardization api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/getcitystandard

Return the standardised city name for a given input

GET

/getcitystandard

Return the standardised city name for a given input

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Interzoid City Data Standardization API through Jentic.

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.

Interzoid City Data Standardization API

Browse all Interzoid APIs

AI ReadinessAI-Ready (A-)76/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to standardise the city 'Saint Louis' to its canonical form, Convert 'NYC' to its standardised city name, Get the canonical version of an international city name like 'Munchen', Standardise a column of messy city values before deduplication

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

55%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Interzoid City Data Standardization API to your agent

Capabilities

Use Cases

Start building with Interzoid City Data Standardization API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Interzoid City Data Standardization API

Jentic AI Readiness Score

Interzoid City Data Standardization API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness