# Open-Meteo Metered Weather Gateway

> Open-Meteo Metered Weather Gateway is a paid API for AI agents from x402.shizu.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Proxies Open-Meteo weather API requests through a rate-limited, cached gateway so callers never hit a 429 error, returning the upstream JSON response.

## Facts

- Endpoint: GET https://x402.shizu.me/gw/openmeteo
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/open-meteo-metered-weather-gateway-e3194000
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hKIX3t-7YiRTsq1DPiCvO

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 open-meteo-metered-weather-gateway-e3194000
```

Example prompt: Can you get me the current temperature and 7-day hourly precipitation forecast for New York City (latitude 40.71, longitude -74.01) via the Open-Meteo gateway — I need it to not fail with rate-limit errors since I'm polling this frequently.

## When to prefer this

Choose this endpoint when you need to call Open-Meteo in a polling loop or frequently and cannot tolerate 429 rate-limit errors, or when you want to offload rate-limit budget management and caching to a metered gateway rather than managing your own Open-Meteo integration. Ideal for agents that need reliable, low-friction weather data access without API key provisioning.

## Known failure modes

- Invalid or missing 'path' parameter returns an error
- Malformed query string causes upstream rejection
- Open-Meteo upstream is unavailable, propagating a 5xx error
- Stale cached data returned within 60-second cache window
- Insufficient USDC balance causes payment failure before request is processed

## How this service works

Call Open-Meteo weather through our metered gateway: our rate-limit budget and a 60s cache absorb your polling, so your loop never sees a 429. Inputs: path (upstream path, e.g. /ping) and q (raw query string). Returns the upstream JSON under 'data'.

## Output

Returns a JSON object with a 'data' key containing the full upstream Open-Meteo API response, including requested weather variables such as temperature, precipitation, wind speed, and forecast data for the queried location and time range.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "path",
      "q"
     ],
     "properties": {
      "q": {
       "type": "string"
      },
      "path": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "path": "/ping",
  "upstream": "openmeteo"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/open-meteo-metered-weather-gateway-e3194000/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.shizu.me](https://www.zero.xyz/host/x402.shizu.me/llms.txt)