5-day / 3-hour weather forecast by coordinates, pay-per-call via MPP on Tempo L2.
What it does
This endpoint provides a 5-day weather forecast with 3-hour time steps, powered by OpenWeather data and sold through the Locus MPP (Micropayment Protocol). You supply latitude and longitude coordinates and receive up to 40 forecast timestamps covering the next 5 days. Optional parameters let you limit the number of returned timestamps (1–40), choose temperature units (standard/Kelvin, metric/Celsius, or imperial/Fahrenheit), and set a language code for weather descriptions.
Payment is handled per-call via the MPP protocol using the Tempo L2 settlement method. The listed price is 8,000 base units of pathUSD (6 decimals), which works out to $0.008 per request. The endpoint accepts POST requests with a JSON body. It is part of a broader OpenWeather service suite on the same host that also offers current weather, air quality, geocoding, reverse geocoding, One Call 3.0, and weather overview endpoints at varying per-call prices.
The OpenAPI spec is well-defined with clear request schemas, required fields, and parameter descriptions. However, no response schema is documented, and the probe did not capture a live 402 challenge on HEAD/GET (the endpoint is POST-only, so this is expected behavior). External documentation is referenced at openweathermap.org/api and a Locus-specific doc at beta.paywithlocus.com/mpp/openweather.md.
Capabilities
Use cases
- —Retrieve a multi-day weather forecast for a given location to plan outdoor activities or logistics
- —Feed forecast data into an AI agent that makes weather-dependent decisions
- —Display upcoming weather conditions in a travel or event planning application
- —Provide weather context for agricultural or supply-chain automation tools
Fit
Best for
- —AI agents needing on-demand weather forecasts without API key management
- —Pay-per-call weather data access with no subscription commitment
- —Applications requiring 3-hour granularity forecasts up to 5 days out
Not for
- —Historical weather data retrieval (this is forecast-only)
- —High-frequency bulk weather polling where a subscription API key would be cheaper
- —Minute-level or hourly-only forecasts (use the One Call endpoint instead)
Quick start
curl -X POST https://openweather.mpp.paywithlocus.com/openweather/forecast-5day \
-H "Content-Type: application/json" \
-d '{"lat": 40.7128, "lon": -74.006, "units": "metric", "cnt": 8}'Example
Request
{
"cnt": 8,
"lat": 40.7128,
"lon": -74.006,
"lang": "en",
"units": "metric"
}Endpoint
Quality
The OpenAPI spec provides a clear request schema with parameter descriptions and pricing metadata, but no response schema is documented and the probe did not capture a live 402 challenge (expected since the endpoint is POST-only and was probed with HEAD/GET). No crawled pages returned useful content. Response format must be inferred from OpenWeather's public API docs.
Warnings
- —No response schema documented in the OpenAPI spec
- —Probe did not capture a 402 challenge because the endpoint only accepts POST; liveness not directly confirmed
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 convention; if different, the $0.008 price may be incorrect
- —External docs at beta.paywithlocus.com/mpp/openweather.md were not crawled
Citations
- —The endpoint charges 8000 base units via Tempo settlement method per callhttps://openweather.mpp.paywithlocus.com
- —Request accepts lat, lon (required), cnt, units, and lang parametershttps://openweather.mpp.paywithlocus.com
- —Part of a broader OpenWeather service suite including current weather, air quality, geocoding, reverse geocoding, One Call, and weather overviewhttps://openweather.mpp.paywithlocus.com
- —API reference available at openweathermap.org/apihttps://openweathermap.org/api