Mapbox

Mapbox gives your app vector maps, address geocoding, and routing. Connect it once and the agent can drop maps, search-as-you-type address fields, and route lines into any project in your account, using your own Mapbox token rather than a shared one.

What you get by connecting it

Once Mapbox is connected, the agent can wire up:

• Maps - a map view styled with Mapbox's vector tiles.
• Geocoding - turning an address into coordinates, and coordinates back into a readable address, including search-as-you-type.
• Routing - directions between points, drawn as a line on the map.

All of this runs on your public token. The first time the agent uses Mapbox in a conversation, it says so in its opening sentence, so you always know when your connection is in play.

A note on the preview: fully interactive pan-and-zoom maps need a development or production build, so they do not run in the Expo Go preview. In the preview the agent uses static map images instead, which look right and behave for most flows. Ask for a development build when you need the fully interactive map.

Connecting it

Mapbox needs a public token (it starts with pk.). You can optionally add a secret token (it starts with sk.) for server-side use.

Find your tokens in your Mapbox account page, under Access tokens.

To connect, go to Dashboard then Connectors then Mapbox and paste the public token into the connector page. You can connect from inside a build too, using the in-chat connect card the moment the agent asks. Connecting requires a paid plan, and once connected every project in the account can use Mapbox.

Saved tokens show as dots, never the value, so the secret token only ever round-trips once. The connector page also has a Test connection control, which re-checks the saved token against Mapbox, and a Disconnect control behind a confirmation step.

Keys and security

Mapbox is a just connect connector. The public token is designed to be public, so the agent embeds it directly where the app needs it. There is no relay and no account access toggle for Mapbox.

The optional secret token is treated as a real secret: it is encrypted at rest with AES-256-GCM, the browser only ever sees that it exists, and the agent never sees the decrypted value. The agent will never ask you for a token in chat - tokens belong on the connector page.

Useful links

• Mapbox documentation: https://docs.mapbox.com
• Appsanic guide: Maps and location

Next

Read Maps and location for the full picture of maps, geocoding, and directions across both Mapbox and Google Maps.