Compute travel-time and distance isochrone polygons via Mapbox, paid per-call over MPP/Tempo.
What it does
The Mapbox Isochrone endpoint, served through the Locus MPP (Micropayment Protocol) gateway, generates isochrone contours — areas reachable from a given coordinate within specified travel times or distances. It wraps the Mapbox Isochrone API and settles payments in pathUSD on the Tempo L2 network at $0.005 per request.
You supply a routing profile (driving, driving-traffic, walking, or cycling), a single lon/lat coordinate, and up to four contour thresholds expressed as minutes (1–60) or meters (1–100,000). The response is a GeoJSON FeatureCollection of linestrings or polygons (when the `polygons` flag is set). Additional parameters let you exclude certain road types (motorway, toll, ferry, unpaved), control noise filtering with `denoise`, and simplify geometry via Douglas-Peucker tolerance (`generalize`).
This endpoint is part of a broader Mapbox suite exposed through the same Locus MPP gateway, which also offers forward/reverse geocoding, directions, matrix routing, map matching, static images, and tilequery — each priced independently. The isochrone endpoint specifically requires a POST with a JSON body. The probe returned 404 on HEAD/GET, which is expected because the endpoint only accepts POST requests. Payment is handled via the MPP 402 challenge flow using the Tempo settlement method.
Capabilities
Use cases
- —Determining areas reachable within a given commute time for real estate search
- —Visualizing delivery zones based on driving or cycling time
- —Site selection analysis by computing walk-time catchment areas around candidate locations
- —Urban planning studies comparing accessibility across transport modes
- —Building interactive maps that show how far a user can travel in N minutes
Fit
Best for
- —Agents needing per-call isochrone computation without a Mapbox API key
- —Applications requiring GeoJSON polygon output for travel-time zones
- —Pay-per-use geospatial analysis without subscription commitments
Not for
- —High-volume batch isochrone jobs where a direct Mapbox subscription would be cheaper
- —Real-time navigation or turn-by-turn routing (use the Directions endpoint instead)
- —Isochrone computation requiring more than 4 simultaneous contour thresholds
Quick start
curl -X POST https://mapbox.mpp.paywithlocus.com/mapbox/isochrone \
-H "Content-Type: application/json" \
-d '{
"profile": "mapbox/driving",
"coordinates": "-73.99,40.73",
"contours_minutes": "5,10,15",
"polygons": true
}'Example
Request
{
"denoise": 1,
"profile": "mapbox/driving",
"polygons": true,
"coordinates": "-73.99,40.73",
"contours_minutes": "5,10,15"
}Endpoint
Quality
Full OpenAPI schema with clear request parameters and pricing is available, but the endpoint returned 404 on HEAD/GET (expected for POST-only), no example response was captured, and crawled pages yielded no additional documentation. Pricing is derivable from the schema's x-payment-info.
Warnings
- —Probe returned 404 on HEAD and GET — endpoint is POST-only; liveness via POST was not confirmed in the probe
- —No example response body is available; response format is inferred to be GeoJSON based on Mapbox API conventions
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals (amount 5000 = $0.005); if decimals differ, the price would change
Citations
- —Isochrone endpoint accepts POST with profile, coordinates, contours_minutes, contours_meters, polygons, denoise, generalize, and exclude parametershttps://mapbox.mpp.paywithlocus.com
- —Payment amount is 5000 in currency 0x20c000000000000000000000b9537d11c60e8b50 via Tempo settlementhttps://mapbox.mpp.paywithlocus.com
- —Endpoint is part of a broader Mapbox suite including geocoding, directions, matrix, map matching, static images, and tilequeryhttps://mapbox.mpp.paywithlocus.com
- —Mapbox Isochrone API documentation available at docs.mapbox.comhttps://docs.mapbox.com/api/navigation/isochrone/https