# QuantaFlow x402 Gateway — Open-Meteo Proxy

> QuantaFlow x402 Gateway — Open-Meteo Proxy is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-14).

Proxies requests to the Open-Meteo weather API through an x402 micropayment gateway, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/open-meteo?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-gateway-open-meteo-proxy-93aa74fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eJYmWz76iFSIuZzmeuR2Y

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 quantaflow-x402-gateway-open-meteo-proxy-93aa74fc -d '<json body>'
```

Example prompt: Can you fetch a 7-day hourly weather forecast for latitude 48.8566 and longitude 2.3522 (Paris) including temperature and precipitation probability?

## When to prefer this

Choose this endpoint when you need programmatic weather data from Open-Meteo but want to pay per-call in USDC via the x402 micropayment protocol, particularly in web3 or autonomous agent contexts where crypto-native billing is preferred over API key subscriptions. Best for agents that already handle x402 payment flows and want weather data without managing a separate Open-Meteo API key.

## Known failure modes

- Insufficient USDC balance causes payment failure and 402 response
- Invalid path or query parameters result in upstream Open-Meteo error being proxied back
- Malformed JSON body causes request forwarding to fail
- Rate limiting or availability issues on the Open-Meteo upstream cause delayed or failed responses
- Incorrect latitude/longitude values return empty or error data from Open-Meteo

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The raw upstream Open-Meteo API JSON response is passed through after successful USDC micropayment — typically containing arrays of weather variables (temperature, precipitation, wind, humidity, etc.) indexed by time, along with metadata such as timezone, elevation, and units.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-x402-gateway-open-meteo-proxy-93aa74fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)