80trust / 100

Seattle Window

by x402-factory in Weather & location

x402 APIPassing, checked 2 h ago

Will it rain in Seattle during your event window — Event-window weather odds for Seattle: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Seattle coordinates built in.

GET https://x402-factory.com/v1/forecast/seattle/window

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
201 ms typical, 500 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

GET https://x402-factory.com/v1/forecast/seattle/window

Each call costs $0.02 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.

GET https://x402-factory.com/v1/forecast/seattle/window

Parameters

ParameterTypeRequiredDescription
endstring (date-time)NoWindow end (ISO-8601), ≤12h after start. Default: start + 6h.
startstring (date-time)NoWindow start (ISO-8601). Default: the top of the next hour.

Example response

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

Example response, 26 lines
{
  "data": {
    "comfort_index": 0.78,
    "expected_precip_mm": 0,
    "rain_probability": 0.15,
    "severity_flags": [],
    "temp_range": {
      "high": 27.7,
      "low": 22.4
    },
    "verdict": "Looks good: warm, highs near 81.9°F, low rain risk.",
    "wind_max": 25.2
  },
  "meta": {
    "data_mode": "live",
    "docs": "https://x402-factory.com/docs/weather.forecast-window.seattle",
    "endpoint": "/v1/forecast/seattle/window",
    "freshness": "realtime",
    "generated_at": "2026-10-05T10:15:58.053Z",
    "request_id": "req_00000000",
    "sources": [
      "stub-model"
    ],
    "version": "1.0.0"
  }
}

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.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://x402-factory.com/v1/forecast/seattle/window'

# 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 - 'https://x402-factory.com/v1/forecast/seattle/window' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402-factory.com%2Fv1%2Fforecast%2Fseattle%2Fwindow
const res = await pay("https://x402-factory.com/v1/forecast/seattle/window");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://x402-factory.com/v1/forecast/seattle/window")
    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
2 h agoPassed402148 ms$0.02
6 h agoPassed402128 ms$0.02
9 h agoPassed402418 ms$0.02
13 h agoPassed402387 ms$0.02
17 h agoPassed402125 ms$0.02
21 h agoPassed402385 ms$0.02
25 h agoPassed402127 ms$0.02
28 h agoPassed402149 ms$0.02
32 h agoPassed402500 ms$0.02
35 h agoPassed402125 ms$0.02
39 h agoPassed402123 ms$0.02
43 h agoPassed402370 ms$0.02
46 h agoPassed402383 ms$0.02
2 days agoPassed402201 ms$0.02
2 days agoPassed402414 ms$0.02