Positionstack MCP integration for AI agents.
Connect AI agents to Positionstack through 2 structured actions, including forward geocode and reverse geocode. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 2
- 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 Positionstack integration exposes
The Positionstack Agent App exposes 2 provider-backed actions for location and data work. Its current contract lets an authorized agent convert an address or place query into positionstack geocoding results and convert coordinates or an ip address into positionstack reverse geocoding results. 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 Positionstack account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Positionstack capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
forward_geocodeREVIEWConvert an address or place query into Positionstack geocoding results.
INPUTS: query / country / region / language / limit
reverse_geocodeREVIEWConvert coordinates or an IP address into Positionstack reverse geocoding results.
INPUTS: query / country / region / language / limit
INPUT CONTRACTS
Know what the action needs before it runs.
forward_geocode
queryREQUIRED- The address, place, latitude/longitude pair, or IP address to geocode.
countryOPTIONAL- Comma-separated 2- or 3-letter country codes used to restrict results.
regionOPTIONAL- Region filter such as a state, county, or city name.
languageOPTIONAL- Preferred response language code, such as en or de.
limitOPTIONAL- Maximum number of results to return, from 1 to 80.
reverse_geocode
queryREQUIRED- Latitude and longitude formatted as latitude,longitude, or an IP address to reverse geocode.
countryOPTIONAL- Comma-separated 2- or 3-letter country codes used to restrict results.
regionOPTIONAL- Region filter such as a state, county, or city name.
languageOPTIONAL- Preferred response language code, such as en or de.
limitOPTIONAL- Maximum number of results to return, from 1 to 80.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Forward Geocode
Convert an address or place query into Positionstack geocoding results. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
forward_geocodeVerify with Reverse Geocode
Convert coordinates or an IP address into Positionstack reverse geocoding results. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
reverse_geocodeSAFETY BOUNDARY
Operate Positionstack with explicit limits
- Authorize Positionstack with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Positionstack 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 Positionstack rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Positionstack task completed successfully.
CONNECTION MODEL
API key
Positionstack API key sent as the access_key query parameter. Get a free key at https://positionstack.com/signup/free/ or manage API keys in APILayer: https://apilayer.com/docs/article/managing-api-keys.
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
- 2
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 Positionstack.