# x402 Weather Forecast (Open-Meteo, Keyless)

> x402 Weather Forecast (Open-Meteo, Keyless) is a paid API for AI agents from x402-v2-mint-weather-forecast.vercel.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-31).

Returns current weather conditions plus a short-range forecast (1–7 days) for any latitude/longitude coordinate using Open-Meteo, with no API key required.

## Facts

- Endpoint: POST https://x402-v2-mint-weather-forecast.vercel.app/v1/weather-forecast?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-weather-forecast-open-meteo-keyless-c8d792db
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_abnkMpZb9HEqf1XvFiTcO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-weather-forecast-open-meteo-keyless-c8d792db -d '<json body>'
```

Example prompt: What's the current weather and 3-day forecast at latitude 48.8566, longitude 2.3522? I need actual data, not a general overview.

## When to prefer this

Choose this endpoint when you need keyless, globally-scoped weather data (current + short forecast) for any latitude/longitude coordinate without managing API keys. It is ideal for agent workflows that already handle x402 micropayments and need a simple, pay-per-call weather primitive. Prefer it over NWS-based siblings when querying non-US coordinates, since it uses Open-Meteo which has global coverage.

## Known failure modes

- Missing or out-of-range lat/lon returns a validation error
- forecast_days outside 1–7 is rejected
- Payment failure via x402 protocol returns 402 status
- Open-Meteo upstream unavailability causes 5xx error
- Invalid coordinate types (e.g. strings instead of numbers) cause schema rejection

## How this service works

Weather current + short forecast via Open-Meteo (keyless). Lat/lon required. Data only — not advice.

## Output

A JSON response with an 'ok' boolean, skill identifier 'weather-forecast', a 'charged' flag indicating the micropayment was processed, and a 'summary' field, along with current conditions and a day-by-day forecast for the requested number of days at the given coordinates.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lat": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "lon": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "timezone": {
   "type": "string",
   "maxLength": 64,
   "description": "Ignored (kept for compatibility); NWS returns the local timeZone"
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "request_id": {
   "type": "string"
  },
  "forecast_days": {
   "type": "integer",
   "default": 3,
   "maximum": 7,
   "minimum": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "skill": "weather-forecast",
  "charged": true,
  "summary": "ok"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-weather-forecast-open-meteo-keyless-c8d792db/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-v2-mint-weather-forecast.vercel.app](https://www.zero.xyz/host/x402-v2-mint-weather-forecast.vercel.app/llms.txt)