Geocodio APIs for AI Agents
Maps GeolocationGeocodingOfficial Vendor DocumentsAPI keyBearer tokenAgent Ready
For Agents
APIs2 in catalogue
Endpoints27 indexed
AuthAPI key / Bearer token
ProvenanceOfficial OpenAPI documents
An agent can geocode US and Canadian addresses to coordinates, reverse geocode coordinate pairs back to addresses, append political, census, school, timezone, and ACS demographic fields, batch process large address lists, and calculate distance or driving time between points.
Geocodio is built for North American address data, pairing accurate US and Canadian geocoding with data appends like congressional districts, census tracts, and ACS demographics that general global geocoders do not return. It suits civic tech, real estate, logistics, and analytics workloads that need political and census geography attached to each address rather than worldwide coverage.
Use for: US and Canadian address geocoding, reverse geocoding, and appending congressional, census, school, timezone, and ACS demographic data, in single, batch, or spreadsheet workflows
Not supported: international coverage, map tile rendering, turn-by-turn routing, POI search, real-time streaming
Credentials: Both APIs authenticate with a single Geocodio API key, passed as the api_key query parameter on both surfaces and additionally accepted as an Authorization bearer token on the geocod-io surface, so one credential covers everything.
All 2 Geocodio OpenAPI documents are vendor-official and indexed by Jentic, kept validated and agent-ready.
Geocodio is a US and Canada focused geocoding service that converts addresses to coordinates and coordinates back to addresses, with optional data appends for congressional districts, state legislative districts, school districts, census tracts, timezones, and ACS demographics. It supports single lookups, batch requests of up to 10,000 addresses, asynchronous spreadsheet jobs, and distance calculation between geocoded points. Two API surfaces are catalogued here, both covering the same North American geocoding and append capabilities across single, batch, and list workflows.
Geocodio API Catalog
2 APIs across 1 product group.
Maps Geolocation2
GeocodioGeocode addresses and reverse geocode coordinates with US/Canada data appends including congressional districts, census tracts, school districts, timezone, and ACS demographics.~16 endpointsGeocodio APIGeocode US and Canadian addresses, reverse-geocode coordinates, and append congressional, census, timezone, and district data - single requests or batch lists.~11 endpoints
Which Geocodio API should I use?
| I want to... | Use |
|---|---|
| Batch geocode very large address lists in one request | Geocodio |
| Append ACS demographics or census tract data to addresses | Geocodio |
| Geocode single addresses and append congressional districts | Geocodio API |
| Upload a spreadsheet and download an enriched file | Geocodio API |
Install Jentic One Beta
Connect the Geocodio APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Geocodio 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.
1
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%2Fgeocod.io" | sh2
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%2Fgeocod.io" | 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: “geocode US and Canadian addresses and append congressional and census data”.
What AI Agents Can Do with Geocodio
Each workflow spans multiple Geocodio APIs. Jentic routes each operation to the right API automatically.
Political geography enrichment for constituent lists
An agent geocodes a list of voter or customer addresses and appends congressional and state legislative districts, then groups the records by district for a report. Either Geocodio surface returns the district assignments on the same call that returns coordinates, so the agent can use whichever variant is imported without changing the field logic.
Example prompt:
Geocode each address with fields=cd,stateleg on /geocode, then group the results by congressional district and produce a per-district count
APIs used
Geocodio + Geocodio API
Bulk spreadsheet geocoding with census appends
An agent uploads a spreadsheet of thousands of addresses, polls until the job finishes, and downloads an enriched file with census tract and demographic fields attached. Both surfaces expose the POST /lists upload plus the /lists status and download endpoints, so the agent can fall back to either variant for the same job.
Example prompt:
Upload the address spreadsheet to /lists, poll /lists/{id} until processed, then call /lists/{id}/download for the enriched file
APIs used
Geocodio + Geocodio API
Address resolution then distance filtering
An agent geocodes a warehouse or store address, then calculates driving or straight-line distance to a set of destination points to decide which are in range. Forward geocoding and the distance calculation are available across both Geocodio surfaces, so the agent can chain them regardless of which variant it loaded.
Example prompt:
Geocode the origin address on /geocode, then use the distance capability against each destination and return points within the max distance threshold
APIs used
Geocodio + Geocodio API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Geocodio APIs by hand means registering your key, deciding per operation whether it rides as the api_key query parameter or a bearer token, and handling the list upload and download flow yourself. Once Jentic One is installed, you or your agent can find and add either Geocodio surface from the Jentic directory and store the key one time.
Permission scoping
Geocodio puts the list id in the URL path, so a rule can pin your agent to one list so it can read and download that list and nothing else. You choose which operations across both surfaces the agent may call, so broader ones like creating lists or forward geocoding are not included unless you add them.
Credential isolation
Your Geocodio API key is stored once, encrypted, by your own Jentic One instance and injected as either the api_key query parameter or the Authorization bearer token at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as geocode an address or append a congressional district, and Jentic returns the matching Geocodio operation with its parameter schema so the agent picks the right endpoint and append fields across either surface.
FAQs
Specific to using Geocodio APIs through Jentic.
What can an agent do across the Geocodio APIs?
An agent can forward geocode US and Canadian addresses to coordinates, reverse geocode coordinates back to addresses, append congressional, state legislative, school, census, timezone, and ACS demographic fields, batch process large lists, run spreadsheet jobs, and calculate distance between points.
Why are there two Geocodio APIs in the directory?
Both entries describe the same Geocodio service from vendor-official specs. The main surface documents 16 endpoints including batch arrays of up to 10,000 addresses and explicit ACS demographic appends, while the geocod-io surface is a compact 11-endpoint variant covering single, batch, and list geocoding. They share the same base URL and credential.
Do the two APIs share one credential?
Yes. A single Geocodio API key works for both surfaces. It is passed as the api_key query parameter on both, and the geocod-io surface additionally accepts it as an Authorization bearer token, so you store one key and use it everywhere.
Which regions do the Geocodio APIs cover?
Coverage is the United States and Canada. Both surfaces bias parsing by a country parameter that defaults to US and accepts CA for Canadian addresses. Neither surface geocodes addresses outside North America, so global workloads need a different provider.
How does an agent choose the right endpoint?
Rather than reading reference docs, an agent searches Jentic by intent such as geocode an address or append a congressional district, and Jentic returns the matching Geocodio operation with its parameter schema so the agent picks the correct endpoint and append fields.
Can an agent enrich addresses with political and census data in one call?
Yes. On both surfaces the fields parameter accepts comma-separated values such as cd, stateleg, school, census, timezone, and acs-demographics, so a single geocode call returns coordinates plus every requested append together.
If you need a different Maps Geolocation vendor
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.