Forward- and reverse-geocode addresses with Mapbox Geocoding API v6 using structured input and permanent vs temporary modes

domain: docs.mapbox.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Call the dedicated forward or reverse v6 geocoding endpoint (forward and reverse are now separate endpoints, unlike v5)
  2. For forward geocoding, prefer structured input fields (address_line1, address_number, street, place, region, postcode, country) over a single free-text query for higher accuracy
  3. Set the permanent parameter explicitly only if you hold a permanent-geocoding entitlement and intend to store results; default behavior for all endpoints is temporary
  4. For reverse geocoding pass longitude,latitude and use types to filter returned feature types
  5. For bulk lookups, POST up to 1000 mixed forward/structured/reverse queries in one batch request as a JSON body

Known gotchas

Related routes

Geocode and reverse-geocode addresses with HERE Geocoding & Search API v7
docs.here.com · 4 steps · unrated
Geocode addresses with Google Maps API without burning budget
google-maps · 4 steps · unrated
Use the public Nominatim geocoder within policy limits or self-host an instance for higher-volume geocoding
operations.osmfoundation.org · 4 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans