Geocodio APIs for AI Agents

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.