3 APIs across 2 product groups. All share one credential.
| I want to... | Use | Why |
|---|---|---|
| Suggest complete US addresses as a user types a partial address | US Autocomplete Pro API | Returns ranked address suggestions from partial input for form entry and validation |
| Pull one or more addresses out of a block of free text | US Extract API | Parses unstructured text and returns USPS-standardized address data |
| Resolve a ZIP code to city, state, county, timezone, and coordinates | Smarty US ZipCode API | Validates single or batched ZIP codes and returns associated location metadata |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Smarty APIs, 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%2Fsmarty.com" | shStep 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%2Fsmarty.com" | 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.
Once connected, ask your agent something like: .
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Smarty APIs by hand means passing the auth key on the query string against three separate base hosts and managing retries yourself. Through Jentic you install once, add the Smarty APIs you need from the Jentic directory, store the key once, and your agent calls all three.
Permission scoping
Each Smarty API exposes a small set of lookup, extract, or autocomplete operations. With your own rules you choose which of those operations the agent may call, so an agent granted only ZIP code lookup cannot run extraction or autocomplete unless you add them.
Credential isolation
Your Smarty API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same key is reused across all three APIs.
Specific to using Smarty APIs through Jentic.
What can an AI agent do across the Smarty APIs?
An agent can autocomplete a partial US address, extract standardized addresses from free text, and look up ZIP code metadata such as city, state, county, timezone, and coordinates. Chained together, these let the agent capture, parse, and validate US location data in one workflow.
Do the Smarty APIs share one credential?
Yes. The autocomplete, extract, and ZIP code APIs all authenticate with the same Smarty API key passed as query parameters, so you configure one credential to reach all three.
Which Smarty API should I use for a given task?
Use the US Autocomplete Pro API to suggest complete addresses from partial input, the US Extract API to pull addresses out of free text, and the US ZipCode API to resolve ZIP codes to location metadata. Many workflows chain two of them, such as extracting an address then validating its ZIP code.
Do the Smarty APIs cover addresses outside the United States?
No. These APIs are scoped to US addresses and US ZIP codes. For international address handling you would need a different provider.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can autocomplete a partial US address, pull structured addresses out of free text, and resolve ZIP codes to city, state, county, timezone, and coordinate metadata. Combined, these let an agent clean and enrich location data end to end without writing per-endpoint HTTP code.
Smarty focuses narrowly on US address and ZIP code data, pairing type-ahead autocomplete, text extraction, and ZIP lookup so location fields are captured, parsed, and validated at each stage. The APIs are consistent in auth and JSON shape, which makes them straightforward to chain in an address-handling workflow.
Use for: Capturing, parsing, and validating US postal addresses and ZIP code data through autocomplete, text extraction, and lookup
Not supported: international addresses, payments, email or messaging, crm records, geocoding routing
Credentials: All three APIs use the same Smarty API key credential passed as query parameters, so one credential covers the autocomplete, extract, and ZIP code endpoints.
All 3 Smarty OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
Smarty provides US address APIs for autocompleting addresses as users type, extracting and standardizing addresses from unstructured text, and looking up ZIP code data such as city, state, county, timezone, and coordinates. The APIs share a single Smarty API key and return structured JSON, so agents can validate and enrich US location data across a single pipeline.
Each workflow spans multiple Smarty APIs. Jentic routes each operation to the right API automatically.
Extract and validate addresses from documents
An agent pulls addresses out of a block of free text, then resolves each ZIP code to its city, state, county, and coordinates to confirm the extracted address is internally consistent before storing it.
Call us-extract on the raw text, then for each returned address look up its ZIP code with us-zipcode and flag mismatches
US Extract API + Smarty US ZipCode API
Capture and enrich address form entries
As a user types, the agent suggests complete US addresses, then enriches the chosen address with ZIP code metadata such as county and timezone to populate downstream fields.
Call us-autocomplete on the partial input, then pass the selected address ZIP to us-zipcode to fill county, timezone, and coordinates
US Autocomplete Pro API + Smarty US ZipCode API
Normalize inbound address text into clean records
The agent extracts addresses from incoming messages or notes and, where only a partial address was found, uses autocomplete to complete it into a standardized form for a clean record.
Run us-extract on the inbound text, then feed any partial results to us-autocomplete to produce a completed, standardized address
US Extract API + US Autocomplete Pro API
Intent-based discovery
Agents search the Jentic directory by intent, such as extract addresses from text or look up a ZIP code, and Jentic returns the matching Smarty operation with its input schema so the agent calls the right endpoint across the portfolio without browsing docs.
What response format do the Smarty APIs return?
All three return structured JSON that an agent can parse and act on directly, so results from one call can be fed into the next without custom formatting.
How do agents find the right Smarty operation?
Agents search the Jentic directory by intent, such as autocomplete a US address or look up a ZIP code, and receive the matching operation with its input schema, so the agent calls the correct endpoint without reading the reference docs.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.