10trust / 100

Weather Forecast

by Lumen Agent Utilities in Weather & location

x402 APIFailing, checked 3 h ago

Weather for any place name or lat/lon (Open-Meteo): current conditions plus up to 16-day daily forecast (temp min/max, precipitation and probability, wind, UV, sunrise/sunset). {location | latitude+longitude, days, units:metric|imperial}.

POST
https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast
Price
$0.001
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
3 h ago, next in 3 days

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 3 h ago: Expected HTTP 402, got 404

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast

Each call costs $0.001 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast
content-type: application/json

{
  "days": 2,
  "location": "Berlin"
}

Parameters

ParameterTypeRequiredDescription
daysnumberNoForecast days, 1-16 (default 7)
latitudenumberNoLatitude (use with longitude instead of location)
locationstringNoPlace name, e.g. Berlin (geocoded)
longitudenumberNoLongitude
unitsstringNoDefault metric One of: metric, imperial.

Example response

The provider's example. We can't check it without paying.

Example response, 63 lines
{
  "current": {
    "apparent_temperature": 13.4,
    "interval": 900,
    "is_day": 1,
    "precipitation": 0,
    "relative_humidity_2m": 51,
    "temperature_2m": 16.5,
    "time": "2026-10-10T14:45",
    "weather_code": 2,
    "wind_direction_10m": 257,
    "wind_speed_10m": 14.8
  },
  "daily": [
    {
      "date": "2026-10-10",
      "precipProbMax": 85,
      "precipSum": 1.5,
      "sunrise": "2026-10-10T07:22",
      "sunset": "2026-10-10T18:23",
      "tMax": 16.7,
      "tMin": 11.1,
      "uvMax": 3.1,
      "weatherCode": 80,
      "windMax": 17.4
    },
    {
      "date": "2026-10-11",
      "precipProbMax": 83,
      "precipSum": 0.9,
      "sunrise": "2026-10-11T07:24",
      "sunset": "2026-10-11T18:20",
      "tMax": 12.7,
      "tMin": 8.4,
      "uvMax": 1.65,
      "weatherCode": 80,
      "windMax": 16.8
    }
  ],
  "latitude": 52.512604,
  "longitude": 13.419517,
  "place": {
    "admin1": "State of Berlin",
    "country": "Germany",
    "geocoder": "open-meteo",
    "name": "Berlin",
    "timezone": "Europe/Berlin"
  },
  "source": "Open-Meteo (CC BY 4.0)",
  "timezone": "Europe/Berlin",
  "units": {
    "apparent_temperature": "°C",
    "interval": "seconds",
    "is_day": "",
    "precipitation": "mm",
    "relative_humidity_2m": "%",
    "temperature_2m": "°C",
    "time": "iso8601",
    "weather_code": "wmo code",
    "wind_direction_10m": "°",
    "wind_speed_10m": "km/h"
  }
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast' \
  -H 'content-type: application/json' \
  --data-raw '{"days":2,"location":"Berlin"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast' \
  -H 'content-type: application/json' \
  --data-raw '{"days":2,"location":"Berlin"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Flumenworks-x402-decoder.onrender.com%2Fv1%2Fweather%2Fforecast&method=POST
const res = await pay("https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "days": 2,
    "location": "Berlin"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://lumenworks-x402-decoder.onrender.com/v1/weather/forecast",
        json={
            "days": 2,
            "location": "Berlin",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
3 h agoExpected HTTP 402, got 404404261 ms-
3 days agoExpected HTTP 402, got 404404272 ms-
4 days agoExpected HTTP 402, got 404404259 ms-
4 days agoExpected HTTP 402, got 404404171 ms-
4 days agoExpected HTTP 402, got 404404233 ms-
Show 10 older checks
4 days agoExpected HTTP 402, got 404404238 ms-
4 days agoExpected HTTP 402, got 404404257 ms-
5 days agoExpected HTTP 402, got 404404560 ms-
5 days agoExpected HTTP 402, got 404404227 ms-
5 days agoExpected HTTP 402, got 404404228 ms-
5 days agoExpected HTTP 402, got 404404217 ms-
5 days agoExpected HTTP 402, got 404404238 ms-
5 days agoExpected HTTP 402, got 404404597 ms-
6 days agoExpected HTTP 402, got 404404611 ms-
6 days agoExpected HTTP 402, got 404404208 ms-