Weather forecast for any point (MET Norway, 9 days) ($0.0018)
weather_forecastRead-onlyIdempotent
PAID ($0.0018 USDC via x402). Forecast for any coordinate from MET Norway's Locationforecast 2.0 (global): the current hour (temperature, humidity, wind, cloud, next-hour rain, symbol), rows up to hours ahead (1 h steps ~2.5 days, then 6 h, each stating its period), and up to 9 UTC-day rows with min/max (incl. MET's 6-hour extremes), total precipitation and the main condition. Times UTC; MET's CC BY 4.0 attribution included. No air quality or alerts. Upstream failure is not charged. Without payment this returns the 402 challenge; the fiatdock-mcp npm package pays automatically. Any answer the tool cannot produce is >= 400 and is NOT charged.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude in decimal degrees, -90 to 90 (required with lon; an empty body answers the published example point) | |
| lon | No | Longitude in decimal degrees, -180 to 180 (required with lat) | |
| days | No | How many daily summary rows (UTC calendar days, today first), 1-9 (default 3) | |
| hours | No | How many hours ahead the `hourly` rows reach, 1-72 (default 24). Steps are 1 h for about the first 2.5 days and 6 h after | |
| payment | No | Base64 of a single x402 v2 PaymentPayload (EIP-3009 transferWithAuthorization on Base USDC). OMIT it on the first call: the 402 you get back carries `howToPay.payloadTemplate` — the exact envelope to fill in — plus the price and the EIP-712 domain. Send it on the second call to complete the purchase; it is forwarded as the PAYMENT-SIGNATURE header, never as body data. Nothing is charged for the 402 itself, and a call that fails after payment settles nothing. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asOf | Yes | ISO time the forecast was read from MET (or revalidated as unchanged) | |
| note | Yes | How to read the rows (UTC times, step lengths, daily rules) and their limits | |
| daily | Yes | One row per UTC day, today first: min/max temperature, total precipitation, main condition | |
| units | Yes | The unit of every number | |
| hourly | Yes | Forecast rows from now for `hours` hours: 1-hour steps for about 2.5 days, then 6-hour steps | |
| source | Yes | Where the data came from | |
| current | Yes | The forecast for the hour now falls in (a forecast, not an observation) | |
| location | Yes | The point forecast (rounded to 4 decimals) and its elevation above sea level as MET models it | |
| defaulted | No | Present only when the body was empty: which point the answer is for, and why | |
| attribution | Yes | The credit MET Norway's licence (CC BY 4.0 / NLOD 2.0) requires — keep it beside any use of the data | |
| forecastEndsAt | Yes | The last forecast time MET publishes for this point (about 9-10 days ahead) | |
| modelUpdatedAt | Yes | When MET last updated this forecast (meta.updated_at) |