Mapbox, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Mapbox account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Developer Tools
- Connects with a key
- 13 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Mapbox is
Mapbox is a platform that provides mapping, navigation, and location data services for developers to integrate into their applications.
You paste in a key from your own Mapbox account. It is kept encrypted, and you can withdraw it from inside Mapbox whenever you like.
One message in, the work done in Mapbox.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Mapbox. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Mapbox account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Mapbox
These are the ready-made tools your AI employee already has in Mapbox. It is not limited to them, but it never has to be taught these.
- Batch GeocodingTool to perform batch forward or reverse geocoding for multiple locations. use when you need consistent geocoding of up to 50 queries in one call.
- Forward GeocodingTool to convert free-form or structured address into geographic coordinates and place features. use when you need forward geocoding from text or address components.
- Get Access TokenTool to extract and validate mapbox access token from connection metadata. use when you need a valid token for downstream actions.
- Permanent Forward GeocodingTool to perform permanent forward geocoding. use when you need enterprise-grade permanent geocoding after confirming account privileges.
- Permanent Reverse GeocodingTool to perform permanent reverse geocoding. use after obtaining coordinates to get cacheable place data. example: lon=-73.989, lat=40.733
- Request Style Embed HTMLTool to retrieve embeddable html for a mapbox style. use when you want to embed a style in an iframe after verifying access.
- Retrieve DirectionsTool to retrieve directions between waypoints. use when you need navigation routes with optional turn-by-turn instructions after confirming origin and destination.
- Retrieve Font Glyph RangesTool to retrieve font glyph ranges as pbf tiles. use when you have confirmed the font name, codepoint range, and valid token.
- Retrieve MatrixTool to retrieve a travel time and distance matrix. use when you need to compute travel durations and distances between multiple locations.
- Retrieve StyleTool to retrieve a mapbox style json. use when you need the full style definition by its id.
- Retrieve Style WMTSTool to retrieve a wmts document for a mapbox style. use when you need the wmts capabilities xml for a specific style id.
- Retrieve Tileset MetadataTool to retrieve metadata for a mapbox tileset. use when you need tilejson details including bounds, zooms, and layer info.
- Reverse GeocodingTool to reverse geocode coordinates into place names. use after obtaining coordinates.
You stay the boss of your Mapbox account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Mapbox account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Mapbox is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Mapbox and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Mapbox
- Can an AI employee really work inside Mapbox?
- Yes. It signs in to your own Mapbox account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Mapbox?
- No. Nothing moves and nothing is replaced. Your records stay in Mapbox, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Mapbox account?
- You paste in a key from your own Mapbox account. It is kept encrypted, and you can withdraw it from inside Mapbox whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Mapbox?
- It has 13 ready-made tools in Mapbox today, among them Batch Geocoding, Forward Geocoding and Get Access Token. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Mapbox and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Mapbox and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Mapbox?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Mapbox is written down with what it did and when.