OpenWeather One Call 3.0 via MPP — current, minutely, hourly, daily forecasts and government alerts in a single request.
What it does
This endpoint wraps OpenWeather's One Call 3.0 API behind the Locus MPP (Micropayment Protocol), letting AI agents fetch a comprehensive weather bundle for any latitude/longitude coordinate with a single per-call payment settled on Tempo L2 in pathUSD. Each call returns current conditions, minutely precipitation for the next hour, hourly forecasts for 48 hours, daily forecasts for 8 days, and government-issued weather alerts — all in one response. You can selectively exclude sections (current, minutely, hourly, daily, alerts) via the `exclude` parameter, and choose units (standard/metric/imperial) and language.
The endpoint accepts POST requests with a JSON body containing `lat` and `lon` (required) plus optional `exclude`, `units`, and `lang` fields. Payment is charged per call at 10,000 base units of pathUSD (6 decimals), which equals $0.01 per request. Settlement uses the Tempo method (pathUSD on Tempo L2). The same Locus MPP service also exposes sibling endpoints for current weather ($0.006), 5-day forecast ($0.008), air quality ($0.006), geocoding ($0.005), reverse geocoding ($0.005), and weather overview ($0.01).
Note that the probe did not capture a live 402 challenge on HEAD/GET — the endpoint only responds to POST. The OpenAPI spec is well-structured with clear request schemas, but response schemas are not documented. Upstream data comes from OpenWeatherMap (openweathermap.org).
Capabilities
Use cases
- —AI agent fetching full weather context for a location before making travel or logistics recommendations
- —Chatbot answering user questions about current and upcoming weather conditions
- —Automated alerting pipeline that checks for government weather warnings at specified coordinates
- —Dashboard or report generation combining current, hourly, and daily forecasts in one call
Fit
Best for
- —Agents needing a comprehensive weather snapshot (current + hourly + daily + alerts) in one request
- —Pay-per-call usage without API key management or subscription commitments
- —Programmatic access to OpenWeather One Call 3.0 data via micropayments
Not for
- —Historical weather data lookups (this endpoint covers current and forecast only)
- —High-volume bulk weather ingestion where a direct OpenWeather subscription would be cheaper
- —Non-weather geospatial data (satellite imagery, terrain, etc.)
Quick start
curl -X POST https://openweather.mpp.paywithlocus.com/openweather/onecall \
-H "Content-Type: application/json" \
-d '{"lat": 40.7128, "lon": -74.006, "units": "metric", "exclude": "minutely"}'Example
Request
{
"lat": 40.7128,
"lon": -74.006,
"lang": "en",
"units": "metric",
"exclude": "minutely,alerts"
}Endpoint
Quality
The OpenAPI spec provides clear request schemas, pricing, and endpoint descriptions, but no response schemas are documented. The probe did not capture a live 402 challenge because the endpoint only accepts POST (HEAD/GET returned 404), so liveness is inferred from the OpenAPI spec rather than confirmed. No crawled documentation beyond the spec was available.
Warnings
- —Probe returned 404 on HEAD and GET — endpoint is POST-only; liveness not directly confirmed via 402 challenge
- —Response schema is not documented in the OpenAPI spec; response structure must be inferred from upstream OpenWeather One Call 3.0 docs
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 convention; not independently verified
Citations
- —The endpoint charges 10,000 base units of pathUSD per call via Tempo settlement methodhttps://openweather.mpp.paywithlocus.com
- —OpenWeather One Call 3.0 provides current, minutely, hourly, daily forecasts and government alertshttps://openweathermap.org/api
- —Additional Locus MPP docs available at skill.md and llms.txthttps://beta.paywithlocus.com/mpp/openweather.md