Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey9 EndpointsREST
For Agents
Geocode and reverse geocode places worldwide, batch geocode many queries at once, calculate driving, walking, and cycling directions, optimise multi-stop routes, and compute isochrone reachability contours. Returns coordinates, structured places, and route geometry.
Use for: I need to geocode an address into latitude and longitude, Reverse geocode a coordinate into a readable place name, Batch geocode a list of addresses in one request, Get driving directions between two coordinates
Not supported: Does not host business listings or reviews, provide live traffic incident feeds, or manage map styles and datasets through this surface. Use for geocoding, directions, optimisation, and isochrone analysis.
The Mapbox API converts text queries and addresses into coordinates, reverse geocodes coordinates back into places, and geocodes many queries in a single batch request. It calculates turn-by-turn directions for driving, walking, and cycling profiles, optimises a route across multiple stops, and computes isochrone contours that show how far you can travel in a time or distance budget. Static map image endpoints render a styled map for a coordinate or bounding box.
Install Jentic One Beta
Connect the Mapbox API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mapbox API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapbox.com%2Fmapbox" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapbox.com%2Fmapbox" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Mapbox API.
Forward geocode a text query or address into coordinates and structured place data
Reverse geocode coordinates back into an address or place name
Batch geocode many forward or reverse queries in a single request
Calculate turn-by-turn directions for driving, walking, or cycling profiles
Optimise a route that visits multiple stops in an efficient order
Compute isochrone contours showing the area reachable within a time or distance budget
Use Cases
Patterns agents use Mapbox API for, with concrete tasks.
★ Location tools for an AI agent
Give an AI agent the ability to geocode places, get directions, and reason about reachability without hand-wiring the Mapbox access-token query parameter. Through Jentic the agent discovers the geocoding, directions, and isochrone operations by intent and calls them with a validated input schema, so a travel or logistics assistant can turn 'where is this address' and 'how do I drive there' into concrete answers.
Geocode '1600 Pennsylvania Ave, Washington DC', then get driving directions from that coordinate to the nearest airport and summarise the distance and duration
Address geocoding at scale
Convert user-entered addresses and place names into coordinates, and reverse geocode raw coordinates back into structured places. The batch endpoint processes many queries in one request, which is useful for cleaning imported address lists or enriching a dataset of coordinates with place names.
Batch geocode a list of 50 store addresses and return the coordinates for each along with a confidence indicator
Route planning and optimisation
Calculate turn-by-turn directions for driving, walking, or cycling, and optimise the order of stops on a multi-stop trip. Directions return route geometry and step guidance, so a delivery or field-service tool can plan efficient routes and present them to a driver.
Optimise a delivery route that visits eight stops starting and ending at the depot, and return the ordered stop sequence
Reachability and service-area analysis
Compute isochrone contours that show the area reachable within a given time or distance budget from a starting point. This backs 'stores within a 20-minute drive' features, service-area maps, and site-selection analysis that depends on travel time rather than straight-line distance.
Compute the area reachable within a 20-minute drive of a coordinate and return the isochrone contour
Key Endpoints
9 endpoints — the mapbox api converts text queries and addresses into coordinates, reverse geocodes coordinates back into places, and geocodes many queries in a single batch request.
METHOD
PATH
DESCRIPTION
GET
/search/geocode/v6/forward
Forward geocode a text query to coordinates
GET
/search/geocode/v6/reverse
Reverse geocode coordinates to addresses
POST
/search/geocode/v6/batch
Batch geocode multiple queries
GET
/directions/v5/mapbox/{profile}/{coordinates}
Get turn-by-turn directions between coordinates
GET
/optimized-trips/v1/mapbox/{profile}/{coordinates}
Get an optimised route visiting multiple stops
GET
/isochrone/v1/mapbox/{profile}/{coordinates}
Get isochrone contours for reachability analysis
GET
/search/geocode/v6/forward
Forward geocode a text query to coordinates
GET
/search/geocode/v6/reverse
Reverse geocode coordinates to addresses
POST
/search/geocode/v6/batch
Batch geocode multiple queries
GET
/directions/v5/mapbox/{profile}/{coordinates}
Get turn-by-turn directions between coordinates
GET
/optimized-trips/v1/mapbox/{profile}/{coordinates}
Get an optimised route visiting multiple stops
GET
/isochrone/v1/mapbox/{profile}/{coordinates}
Get isochrone contours for reachability analysis
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Mapbox API
- Foundational (D)46/100
79
Foundational Compliance62
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability15
Security74
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
79
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
3%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
47%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
32%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
74
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
74%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mapbox API by hand means appending your access token to the `access_token` query parameter on every request and handling profile and coordinate templating in the directions and isochrone paths. Through Jentic you install once, import Mapbox from the API Directory, store the token once, and your agent calls the geocoding, directions, and isochrone operations directly.
Permission scoping
You choose the operations your agent may call, so you can allow forward geocoding and directions while leaving out batch operations or static-image rendering. Because the geocoding query travels in the request rather than a resource id in the path, rules bound which operations run, not which place is queried.
Credential isolation
Your Mapbox access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'geocode an address' or 'optimise a route', and Jentic returns the matching Mapbox operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mapbox API through Jentic.
What authentication does the Mapbox API use?
The Mapbox API authenticates with an access token passed as the `access_token` query parameter on each request, per its OpenAPI spec. You create a token in your Mapbox account dashboard. Through Jentic the token is stored once and injected at call time, so your agent never places it in the query string itself.
Can I geocode and reverse geocode addresses with the Mapbox API?
Yes. The forward geocoding endpoint turns a text query or address into coordinates and structured place data, the reverse endpoint turns coordinates back into a place, and the batch endpoint handles many queries in a single request. This makes it a good fit for both interactive lookups and bulk address cleanup.
Is there a Mapbox MCP server?
You do not need an MCP server to give your agent the Mapbox API. Jentic connects it directly from the API Directory: import it, store your access token once, and your agent calls the geocoding, directions, and isochrone operations on demand. Nothing extra runs, and no server tool definitions sit in the agent's context between calls.
Can I limit what my agent is allowed to do with the Mapbox API?
Yes. Write a rule that allows only the operations you need, such as forward geocoding and directions, so the agent can look up places and plan routes but cannot call anything you have not listed. Every call it makes is logged, so you can audit exactly which operations ran.
What are the rate limits for the Mapbox API?
The OpenAPI spec does not specify rate limits. Limits depend on your Mapbox account tier and vary by service, so check the Mapbox documentation at https://docs.mapbox.com/api/ for the quota that applies to your token.
How do I get directions with the Mapbox API through Jentic?
Search Jentic for 'get driving directions' to find the directions operation, which returns route geometry and step-by-step guidance between coordinates, and pair it with the geocoding operation to convert addresses to coordinates first. Jentic returns each operation with its input schema so your agent calls it correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED