Query Mapbox tilesets by coordinate to retrieve nearby map features, paid per call via MPP/Tempo.
What it does
The Mapbox Tilequery endpoint, served through the Locus MPP (Micropayment Protocol) gateway, lets you query Mapbox vector tilesets at a specific longitude/latitude and retrieve GeoJSON features within a configurable radius. It supports querying up to 25 comma-separated tileset IDs in a single request, filtering by geometry type (polygon, linestring, point) and layer name, deduplication, and adjustable result limits (1–50). This is useful for point-in-polygon lookups, spatial feature discovery, and enriching coordinates with surrounding map data.
Payment is handled via the MPP protocol using the Tempo settlement method. Each Tilequery call costs 5000 base units of pathUSD (currency 0x20c…b50), which at 6 decimals equals $0.005 per request. The endpoint is a POST that accepts a JSON body with required fields tileset_id, longitude, and latitude, plus optional radius, limit, dedupe, geometry, and layers parameters.
The endpoint is part of a broader Mapbox suite exposed through Locus MPP that also includes forward/reverse geocoding, directions, matrix routing, isochrone generation, map matching, and static image rendering. Note that the probe returned 404 on HEAD/GET for this specific path, which is expected since the endpoint only accepts POST requests. The OpenAPI spec is well-defined with full request schemas and payment metadata.
Capabilities
Use cases
- —Determine what geographic features (buildings, parks, roads) exist at or near a given coordinate
- —Perform point-in-polygon checks to identify which administrative boundary or zone a location falls within
- —Enrich GPS coordinates with contextual map data from Mapbox tilesets
- —Query multiple tilesets simultaneously to gather layered spatial information for a location
- —Filter nearby map features by geometry type or layer name for targeted spatial analysis
Fit
Best for
- —Agents needing on-demand spatial feature lookups without managing Mapbox API keys
- —Point-in-polygon and proximity queries against Mapbox vector tilesets
- —Pay-per-call spatial data enrichment workflows
Not for
- —Bulk tile rendering or raster map tile serving
- —Streaming real-time map data for interactive web maps
- —Use cases requiring free or subscription-based pricing rather than per-call micropayments
Quick start
curl -X POST https://mapbox.mpp.paywithlocus.com/mapbox/tilequery \
-H "Content-Type: application/json" \
-H "Authorization: <MPP_PAYMENT_TOKEN>" \
-d '{
"tileset_id": "mapbox.mapbox-streets-v8",
"longitude": -73.99,
"latitude": 40.73,
"radius": 100,
"limit": 5
}'Example
Request
{
"limit": 5,
"dedupe": true,
"layers": "building,landuse",
"radius": 100,
"geometry": "polygon",
"latitude": 40.73,
"longitude": -73.99,
"tileset_id": "mapbox.mapbox-streets-v8"
}Endpoint
Quality
The OpenAPI spec provides a complete request schema with field descriptions and payment metadata for the Tilequery endpoint. However, no response schema or example response is available, the probe returned 404 (expected for POST-only endpoint but liveness not confirmed via POST), and crawled pages yielded no additional documentation. Price is clearly derivable from the spec.
Warnings
- —Endpoint probe returned 404 on HEAD and GET; the endpoint likely only accepts POST, but POST-based liveness was not confirmed
- —No response schema or example response is documented in the OpenAPI spec
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on Tempo convention; if decimals differ, the stated price of $0.005 would be incorrect
Citations
- —Tilequery endpoint charges 5000 base units via Tempo settlement methodhttps://mapbox.mpp.paywithlocus.com
- —Tilequery accepts tileset_id, longitude, latitude as required fields with optional radius, limit, dedupe, geometry, and layershttps://mapbox.mpp.paywithlocus.com
- —The Mapbox MPP service includes geocoding, directions, isochrones, matrix routing, map matching, static maps, and spatial querieshttps://mapbox.mpp.paywithlocus.com
- —Mapbox API reference available at docs.mapbox.com/api/https://docs.mapbox.com/api/)