Human-readable weather overview for any location, pay-per-call via MPP on Tempo L2.
What it does
The Weather Overview endpoint is part of the OpenWeather suite served through the Locus MPP (Micropayment Protocol) gateway. It returns a weather overview for a given latitude/longitude coordinate, optionally for a specific date (today or tomorrow). The endpoint accepts POST requests with a JSON body containing lat, lon, and optional date (YYYY-MM-DD) and units (standard/metric/imperial) parameters. Payment is settled per-call on Tempo L2 using pathUSD at $0.01 per request.
This endpoint is one of seven OpenWeather paths available through the same MPP gateway. Sibling endpoints cover current weather ($0.006), 5-day forecasts ($0.008), air quality ($0.006), geocoding ($0.005), reverse geocoding ($0.005), and the comprehensive One Call 3.0 suite ($0.01). All endpoints use the same POST-with-JSON-body pattern and the same Tempo/pathUSD settlement method.
The underlying data comes from OpenWeatherMap's API. The Weather Overview path likely corresponds to OpenWeather's human-readable weather summary feature, which provides a natural-language description of weather conditions rather than raw numerical data. Note that the probe did not capture a live 402 challenge on HEAD/GET (the endpoint returned 404, consistent with it being POST-only), so liveness is inferred from the well-formed OpenAPI spec and the broader gateway behavior.
Capabilities
Use cases
- —Get a human-readable weather summary for a travel destination
- —Provide daily weather briefings in chatbot or agent workflows
- —Generate weather context for content or notification systems
- —Combine with geocoding endpoint to go from city name to weather overview
Fit
Best for
- —AI agents needing natural-language weather context per location
- —Applications that want a concise weather narrative rather than raw data
- —Pay-as-you-go weather lookups without API key management
Not for
- —Historical weather data analysis over long time ranges
- —High-frequency bulk weather polling (per-call cost adds up)
- —Minute-level precipitation nowcasting
Quick start
curl -X POST https://openweather.mpp.paywithlocus.com/openweather/weather-overview \
-H "Content-Type: application/json" \
-d '{"lat": 40.7128, "lon": -74.006, "units": "metric"}'Example
Request
{
"lat": 40.7128,
"lon": -74.006,
"date": "2025-01-15",
"units": "metric"
}Endpoint
Quality
Full OpenAPI schema with clear request parameters and pricing for all seven endpoints. However, no live 402 challenge was captured (POST-only endpoint probed with HEAD/GET), no response schema or example response is available, and crawled pages all returned 404 JSON errors. Liveness is inferred but not confirmed.
Warnings
- —Probe returned 404 on HEAD and GET; endpoint is POST-only so liveness is inferred from OpenAPI spec, not confirmed via 402 challenge
- —No response schema or example response provided in the OpenAPI spec
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 convention; if decimals differ, stated prices would be wrong
- —External docs at https://beta.paywithlocus.com/mpp/openweather.md were not crawled
Citations
- —Weather Overview endpoint charges 10000 base units via Tempo method with intent 'charge'https://openweather.mpp.paywithlocus.com
- —OpenAPI spec lists seven endpoints including weather-overview, current-weather, forecast-5day, air-quality, geocode, reverse-geocode, and onecallhttps://openweather.mpp.paywithlocus.com
- —API reference and homepage point to openweathermap.orghttps://openweathermap.org/api
- —LLM-specific docs available at beta.paywithlocus.comhttps://beta.paywithlocus.com/mpp/openweather.md