Resolve addresses and place names to coordinates using maintained geographic data.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
163 available services15 capability categoriesOpen discovery · no login
Choosing geocoding for your task
Choose by geographic coverage, match quality and allowed use of results. Distinguish address lookup from business or point-of-interest search.
Before you proceed: Test ambiguous addresses and coordinate order. Confirm whether results may be stored and whether the provider requires a particular map display.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Geocoding
5 services · Catalog updated 2026-11-10 · See each listing’s review date
Create a Mapbox account and access token, configure billing and decide whether results will be stored. Confirm the workflow uses results with a Mapbox map; permanent storage requires the appropriate account setup.
Our integration playbook Set the result-storage policy before building an address lookup workflow
Create a Geoapify account and project, generate an API key and configure restrictions suitable for the client. Choose a plan and implement the required Geoapify and source-data attribution.
Our integration playbook Resolve the location before trusting a route estimate
Create a Smarty account, obtain secret API credentials and activate licences for the APIs you need. The MCP bulk-address tool requires explicit user confirmation of its lookup count.
Our integration playbook Preserve uncertain address details instead of silently completing them
Create an account and API key, confirm country and field coverage, and choose a plan and usage limit. Self-serve and Enterprise use different accounts and endpoints.
Our integration playbook Budget by requested fields and review approximate matches before joining datasets
Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.
GET /api/agent-services?capability=email
GET /api/agent-services?interface=mcp
GET /api/agent-services?payment=x402-wallet
GET /api/agent-services?payment=mpp-wallet
GET /api/agent-services?payment=no-payment
GET /api/agent-services?id=e2b
You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.
Check what you need from your owner
Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.
Confirm your payment path
Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.