# x402 Weather API Hub – OpenWeather Endpoint

> x402 Weather API Hub – OpenWeather Endpoint is a paid API for AI agents from x402-weather.vercel.app, paid per call via x402, $0.075/call, status unknown (last checked 2026-10-21).

Fetches weather data from OpenWeather via a path-routed proxy endpoint, paid per call using x402 USDC micropayments

## Facts

- Endpoint: POST https://x402-weather.vercel.app/api/open-weather/%7Bpath%7D?utm_source=zero.xyz
- Price: $0.075/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-weather-api-hub-openweather-endpoint-71c187fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dEUNZcWQ5j5oYrQ5-3XA6

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-api-hub-openweather-endpoint-71c187fd -d '<json body>'
```

Example prompt: What's the current weather in London right now? Use the OpenWeather endpoint to pull the latest conditions.

## When to prefer this

Choose this endpoint when you need weather data from OpenWeather and want to pay per call using x402 USDC micropayments without managing a traditional API subscription. Ideal for AI agents or autonomous workflows that need weather lookups on demand and can handle crypto micropayments natively. Prefer over direct OpenWeather API access when you want frictionless per-call billing without API key management.

## Known failure modes

- Invalid or unrecognized location query returns an error or empty data
- Missing required 'query' field results in a 400-level validation error
- Payment failure via x402 micropayment protocol blocks the request
- Invalid path parameter results in routing to wrong or nonexistent sub-endpoint
- RapidAPI upstream outage causes 502/503 errors
- Ambiguous city name (e.g. 'Springfield') may return unexpected location data

## How this service works

21 paid weather API endpoints powered by x402 micropayments

## Output

Returns a JSON object with a 'data' field containing the OpenWeather API response for the queried location, including current conditions such as temperature, humidity, wind, and general weather status as provided by the underlying RapidAPI-powered OpenWeather provider.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "Location query (e.g. 'London' or '40.7128,-74.0060')"
  },
  "location": {
   "type": "string",
   "description": "City name or coordinates"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "Response data from the underlying RapidAPI provider"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-weather-api-hub-openweather-endpoint-71c187fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-weather.vercel.app](https://www.zero.xyz/host/x402-weather.vercel.app/llms.txt)