Usage of the Directions API, Optimization API, Map Matching API, and Isochrone API are all measured in API requests. The number of requests included in the free tier and the cost per request beyond what is included in the free tier are the same across APIs. A request that contains multiple waypoints - see the API documentation for service-specific details is billed as a single API request.
The Mapbox Matrix API is billed by elements rather than by requests, since this API handles requests of widely varying sizes. For instance, one request from the Matrix API can be many different origin and destination pairs, so one request from the Matrix API is equal to the number of sources multiplied by the number of destinations. The minimum number of elements included in a single request would be two (1 source x 2 destinations), while the maximum number of elements included in a single request would be 625 (25 sources x 25 destinations).
By default, the Mapbox Matrix API returns a symmetric matrix, using all input coordinates as both sources and destinations. In this case, the number of elements would be the number of coordinates2. You may also generate an asymmetric matrix, with only some coordinates as sources or destinations. In that case, the number of elements per request would be the number of sources multiplied by the number of destinations.
Read more about how the Mapbox Matrix API works on our comprehensive How Directions Works guide.
For high volume use of the Mapbox Matrix API, contact our sales team for pricing.
We have several tools across platforms that allow you to integrate Mapbox Directions-related APIs into your existing applications, including:
When using a directions-related library or plugin with a Mapbox map, you will be billed for the number of directions-related requests made in addition to map loads, Maps MAUs, or tile requests (read the Web maps or Mobile applications section above to see which applies to your application).