# x402 Weather API Hub – Dynamic Path Weather Endpoint

> x402 Weather API Hub – Dynamic Path Weather 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).

Retrieves weather data for a specified location via a dynamic path on the x402 micropayment-gated weather API hub

## Facts

- Endpoint: POST https://x402-weather.vercel.app/api/weather338/%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-dynamic-path-weather-endpoint-c3e6ab2d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sRblADlzHyYeSyvhY1Ow3

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-dynamic-path-weather-endpoint-c3e6ab2d -d '<json body>'
```

Example prompt: What's the current weather in Tokyo? Use the x402 Weather API Hub to look it up — query location 'Tokyo, Japan'.

## When to prefer this

Choose this endpoint when you need weather data and are operating in an x402 micropayment-enabled environment, particularly when building autonomous AI agents that can pay per call in USDC without requiring API key management. Prefer this over traditional weather APIs when you want per-call billing with no subscription overhead and are already integrated with the x402 payment protocol.

## Known failure modes

- Invalid or unrecognized location query returns empty or error data
- Payment failure if x402 USDC balance is insufficient, blocking the request
- Unknown or invalid path parameter results in 404 or unrouted request
- RapidAPI upstream provider downtime causes failed or delayed responses
- Malformed input (missing required `query` field) results in a validation error

## How this service works

21 paid weather API endpoints powered by x402 micropayments

## Output

Returns a JSON object containing a `data` field with the weather response payload from the underlying RapidAPI weather provider, including current conditions and related meteorological data for the queried location.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "Location query string"
  },
  "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-dynamic-path-weather-endpoint-c3e6ab2d/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)