# x402 Weather API Hub – DataNest Weather Proxy

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

Proxies weather data requests to DataNest weather APIs via x402 micropayments, returning location-based weather information for a given query or coordinates

## Facts

- Endpoint: POST https://x402-weather.vercel.app/api/datanest-weather/%7Bpath%7D?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-weather-api-hub-datanest-weather-proxy-cfe94f7f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i0y_eEFKx224Tk7CNxmNy

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-datanest-weather-proxy-cfe94f7f -d '<json body>'
```

Example prompt: What's the current weather in San Francisco? Use the DataNest weather API to pull the latest conditions.

## When to prefer this

Choose this endpoint when you need programmatic weather data access with per-call micropayment billing via x402/USDC, especially in agent workflows where you want to pay only for what you use without a subscription. Prefer this over traditional weather APIs when operating in a crypto-native or x402-enabled payment environment.

## Known failure modes

- Invalid or unrecognized location query returns empty or error data
- Insufficient USDC balance causes x402 payment failure and request rejection
- Malformed request body missing required `query` field returns validation error
- Upstream DataNest/RapidAPI provider downtime causes 502 or timeout
- Ambiguous location name (e.g. 'Springfield') may return data for unexpected city

## How this service works

21 paid weather API endpoints powered by x402 micropayments

## Output

Returns a JSON object with a `data` field containing weather information from the underlying DataNest/RapidAPI provider, including meteorological details such as temperature, conditions, and other weather metrics for the queried location.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "Location query for weather data"
  },
  "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-datanest-weather-proxy-cfe94f7f/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)