Convert latitude/longitude coordinates to place names via OpenWeather's reverse geocoding API, paid per call over MPP.
What it does
This endpoint provides reverse geocoding powered by OpenWeather data, served through the Locus MPP (Micropayment Protocol) gateway. Given a latitude and longitude, it returns matching place names, including city, state, and country information. You can request up to 5 results per call.
The endpoint accepts POST requests with a JSON body containing required `lat` and `lon` fields, plus an optional `limit` parameter (1–5, default 5). Each call costs 5,000 base units of pathUSD on Tempo L2, which equals $0.005 (half a cent) per request. Payment is handled via the MPP charge intent — no API key or subscription required; the agent pays per call.
This reverse geocode endpoint is part of a broader OpenWeather suite available on the same MPP gateway, which includes current weather, 5-day forecasts, air quality, forward geocoding, One Call 3.0, and weather overviews. Note that the probe did not receive a 402 challenge when hitting this specific path with HEAD/GET (it returned 404), which is consistent with the OpenAPI spec declaring it as a POST-only endpoint. The OpenAPI schema is well-defined with clear field descriptions.
Capabilities
Use cases
- —Converting GPS coordinates from a device or sensor into human-readable place names
- —Enriching location-tagged data (photos, logs, IoT events) with city/country metadata
- —Building location-aware agents that need to describe where something is
- —Resolving coordinates returned by other weather or mapping APIs into named locations
Fit
Best for
- —AI agents needing pay-per-call reverse geocoding without API key management
- —Low-volume or sporadic geocoding where a subscription is overkill
- —Workflows already using Tempo/pathUSD micropayments on Locus MPP
Not for
- —High-volume batch geocoding where per-call costs add up versus flat-rate plans
- —Use cases requiring full street-level address resolution (this returns city/state/country level)
Quick start
curl -X POST https://openweather.mpp.paywithlocus.com/openweather/reverse-geocode \
-H "Content-Type: application/json" \
-d '{"lat": 51.5074, "lon": -0.1278, "limit": 3}'Example
Request
{
"lat": 51.5074,
"lon": -0.1278,
"limit": 3
}Endpoint
Quality
The OpenAPI schema is complete with field descriptions and payment info, but no response schema or example response is provided. The endpoint returned 404 on HEAD/GET probes, which is expected for a POST-only route, but means we lack a live 402 challenge confirmation for this specific path. No crawled documentation beyond the OpenAPI spec was available.
Warnings
- —No 402 challenge was captured for this specific endpoint — HEAD and GET returned 404; the endpoint is POST-only per the OpenAPI spec, so liveness could not be independently confirmed via the probe.
- —No response schema is documented — the shape of the returned geocoding data is unknown from the provided materials.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on the Tempo/MPP convention; if this assumption is wrong, the stated price of $0.005 would be incorrect.
Citations
- —Reverse geocode endpoint accepts POST with lat, lon, and optional limit (1–5), charged at 5000 base units via Tempohttps://openweather.mpp.paywithlocus.com
- —Part of a broader OpenWeather suite including current weather, 5-day forecast, air quality, geocoding, One Call, and weather overviewhttps://openweather.mpp.paywithlocus.com
- —API reference and homepage at openweathermap.org; LLM docs at beta.paywithlocus.com/mpp/openweather.mdhttps://openweathermap.org/api