Reverse geocode coordinates to addresses via Mapbox, paid per-call over MPP/Tempo.
What it does
This endpoint provides reverse geocoding powered by Mapbox through the Locus MPP (Micropayment Protocol) gateway. Given a longitude and latitude, it returns place names, addresses, and geographic feature information. Payment is settled per-call via the Tempo method on pathUSD at $0.00375 per request.
The reverse geocode endpoint accepts required longitude and latitude parameters along with optional filters: country codes (ISO 3166-1 alpha-2), IETF language tags for localized results, result limits (1–5, default 1), feature type filters (country, region, postcode, district, place, locality, neighborhood, address, street, block), and worldview codes. It is part of a broader Mapbox suite available through the same Locus MPP gateway, which also exposes forward geocoding, directions, matrix routing, isochrones, map matching, static images, and tile queries.
The endpoint is a POST-only JSON API. The probe returned 404 on HEAD and GET, which is expected since the OpenAPI spec defines only a POST method. The OpenAPI schema is well-documented with full request body definitions. No response schema is provided, but Mapbox's own documentation describes GeoJSON feature collections as the standard output format.
Capabilities
Use cases
- —Converting GPS coordinates from a mobile device into a human-readable address
- —Enriching location data in analytics pipelines with place names and regions
- —Building location-aware chatbots that describe where a user is
- —Tagging photos or sensor data with geographic context
- —Resolving delivery drop-off coordinates to street addresses
Fit
Best for
- —Agents needing pay-per-call reverse geocoding without API key management
- —Programmatic coordinate-to-address lookups with language localization
- —Lightweight integrations that want Mapbox quality without a Mapbox account
Not for
- —High-volume batch geocoding where a direct Mapbox subscription would be cheaper
- —Use cases requiring the full Mapbox response schema guarantees documented in Mapbox's own API reference
Quick start
curl -X POST https://mapbox.mpp.paywithlocus.com/mapbox/geocode-reverse \
-H "Content-Type: application/json" \
-d '{"longitude": -73.9857, "latitude": 40.7484}'Example
Request
{
"limit": 1,
"types": "address",
"language": "en",
"latitude": 40.7484,
"longitude": -73.9857
}Endpoint
Quality
The OpenAPI spec is detailed with full request schemas and clear pricing metadata, but no response schema or example responses are provided. The probe returned 404 because it used HEAD/GET rather than POST, so liveness is not confirmed but likely given the well-structured OpenAPI definition. Crawled pages returned only generic 404 JSON; no additional documentation was retrieved.
Warnings
- —Endpoint returned 404 on HEAD and GET probes; it is POST-only per the OpenAPI spec, so liveness is not definitively confirmed
- —No response schema is documented — output format must be inferred from Mapbox's own API docs
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals; if incorrect, the stated price of $0.00375 would be wrong
Citations
- —Reverse geocode endpoint charges 3750 base units via Tempo method with currency 0x20c000000000000000000000b9537d11c60e8b50https://mapbox.mpp.paywithlocus.com
- —Request body requires longitude and latitude with optional country, language, limit, types, and worldview parametershttps://mapbox.mpp.paywithlocus.com
- —Part of a broader Mapbox suite including forward geocoding, directions, isochrones, matrix, map matching, static images, and tilequeryhttps://mapbox.mpp.paywithlocus.com
- —Mapbox API reference available at docs.mapbox.com/api/https://docs.mapbox.com/api/Mapbox