Geocodio MCP integration for AI agents.
Connect AI agents to Geocodio through 4 structured actions, including batch reverse geocode, geocode batch, and single geocode. Review authentication, inputs…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Geocodio integration exposes
The Geocodio Agent App exposes 4 provider-backed actions for location and data work. Its current contract lets an authorized agent reverse geocode multiple coordinate pairs in one batch request and return geocodio batch results, geocode multiple addresses in one batch request and return geocodio batch results, and geocode a single address and return the official geocodio response payload. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Geocodio account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Geocodio capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_reverse_geocodeREVIEWReverse geocode multiple coordinate pairs in one batch request and return Geocodio batch results.
INPUTS: coordinates / fields / limit
geocode_batchREVIEWGeocode multiple addresses in one batch request and return Geocodio batch results.
INPUTS: addresses / fields / limit
single_geocodeREVIEWGeocode a single address and return the official Geocodio response payload.
INPUTS: q / street / street2 / city / state
single_reverse_geocodeREVIEWReverse geocode a single latitude and longitude pair and return the official Geocodio response payload.
INPUTS: lat / lng / fields / limit / format
INPUT CONTRACTS
Know what the action needs before it runs.
batch_reverse_geocode
coordinatesREQUIRED- The coordinate strings to reverse geocode in one batch request.
fieldsOPTIONAL- A comma-separated list of Geocodio data append codes.
limitOPTIONAL- The maximum number of results per coordinate.
geocode_batch
addressesREQUIRED- The address strings to geocode in one batch request.
fieldsOPTIONAL- A comma-separated list of Geocodio data append codes.
limitOPTIONAL- The maximum number of results per address.
single_geocode
qOPTIONAL- The full address string to geocode.
streetOPTIONAL- The street address component.
street2OPTIONAL- The secondary street address component.
cityOPTIONAL- The city name used for the lookup.
stateOPTIONAL- The state or province code used for the lookup.
single_reverse_geocode
latREQUIRED- The latitude to reverse geocode.
lngREQUIRED- The longitude to reverse geocode.
fieldsOPTIONAL- A comma-separated list of Geocodio data append codes.
limitOPTIONAL- The maximum number of results to return.
formatOPTIONAL- Return Geocodio's simplified single-result response format.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Reverse Geocode
Reverse geocode multiple coordinate pairs in one batch request and return Geocodio batch results. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_reverse_geocodeVerify with Geocode Batch
Geocode multiple addresses in one batch request and return Geocodio batch results. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
geocode_batchSAFETY BOUNDARY
Operate Geocodio with explicit limits
- Authorize Geocodio with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Geocodio data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Geocodio rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Geocodio task completed successfully.
CONNECTION MODEL
API key
Geocodio API key used as the api_key query parameter. Create or manage it at https://dash.geocod.io/apikey.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Geocodio.