Pay-per-call current weather data via OpenWeather, settled on Tempo L2 with pathUSD.
What it does
This MPP endpoint provides current weather conditions for any location on Earth, powered by OpenWeather data and brokered through the Locus MPP (Micropayment Protocol) gateway. You send a POST request with latitude and longitude coordinates and receive current weather data in return. Each call costs 6,000 base units of pathUSD (0.006 pathUSD assuming 6 decimals) settled on Tempo L2.
The endpoint accepts optional parameters for unit system (standard/Kelvin, metric/Celsius, or imperial/Fahrenheit) and language code for weather descriptions. It is part of a broader OpenWeather service suite on the same MPP host that includes 5-day forecasts, air quality, geocoding, reverse geocoding, One Call 3.0 full forecast, and weather overview — each priced separately.
Note that the endpoint is a POST-only route. The probe returned 404 on HEAD and GET, which is expected since the OpenAPI spec defines only a POST method. No 402 challenge was captured during probing, so liveness could not be confirmed via the standard MPP handshake, but the OpenAPI schema is fully defined with request body schema, payment info, and endpoint paths. The upstream data source is OpenWeatherMap (openweathermap.org).
Capabilities
Use cases
- —AI agents fetching live weather conditions for a given location
- —Chatbots providing current temperature and weather descriptions to users
- —Automated dashboards displaying real-time weather for multiple coordinates
- —Travel planning tools that need current conditions at a destination
Fit
Best for
- —Agents needing pay-per-call weather without API key management
- —Low-volume or sporadic weather lookups where a subscription is overkill
- —Crypto-native applications settling micropayments on Tempo L2
Not for
- —High-volume weather ingestion where a flat-rate subscription is cheaper
- —Historical weather data retrieval (not offered by this endpoint)
- —Applications that cannot settle payments via Tempo L2 / pathUSD
Quick start
curl -X POST https://openweather.mpp.paywithlocus.com/openweather/current-weather \
-H "Content-Type: application/json" \
-d '{"lat": 40.7128, "lon": -74.006, "units": "metric"}'Example
Request
{
"lat": 40.7128,
"lon": -74.006,
"lang": "en",
"units": "metric"
}Endpoint
Quality
Full OpenAPI schema with request body definitions and payment info is available, but no 402 challenge was captured (POST-only endpoint probed with HEAD/GET), no response schema is documented, and no example response is available. Liveness is unconfirmed. The currency address is present but decimals are not explicitly stated, requiring inference.
Warnings
- —Liveness unconfirmed: probe used HEAD/GET but endpoint is POST-only; no 402 challenge was captured.
- —No response schema defined in the OpenAPI spec — response structure must be inferred from OpenWeatherMap docs.
- —Currency decimals not explicitly provided; 0.006 pathUSD price assumes 6 decimals for pathUSD (standard for USD stablecoins). If decimals differ, the actual price changes.
- —Crawled pages all returned 404 JSON errors; no additional documentation was retrievable from the host itself.
Citations
- —OpenAPI spec defines a POST endpoint at /openweather/current-weather with lat/lon required parametershttps://openweather.mpp.paywithlocus.com
- —Payment amount is 6000 base units of pathUSD settled via Tempo methodhttps://openweather.mpp.paywithlocus.com
- —Upstream API reference is at openweathermap.org/apihttps://openweathermap.org/api
- —LLM-readable docs referenced at https://beta.paywithlocus.com/mpp/openweather.mdhttps://beta.paywithlocus.com/mpp/openweather.md