# x402 Weather API Hub – Visual Crossing Proxy

> x402 Weather API Hub – Visual Crossing 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 requests to the Visual Crossing weather API endpoint via x402 micropayment-gated access, returning weather data for a given location

## Facts

- Endpoint: POST https://x402-weather.vercel.app/api/visual-crossing/%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-visual-crossing-proxy-b6fbc315
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_I3MgKymjOqHoJFE9XceRo

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-visual-crossing-proxy-b6fbc315 -d '<json body>'
```

Example prompt: What's the current weather in Austin, Texas right now — temperature, conditions, and anything notable?

## When to prefer this

Use this endpoint when you need weather data specifically from the Visual Crossing provider and are operating in an x402 micropayment-enabled environment. It is ideal for AI agents that have USDC wallets and need pay-per-call weather lookups without API key management. Prefer this over alternatives when Visual Crossing's data quality or historical weather coverage is required.

## Known failure modes

- Invalid or unrecognized location query returns an error or empty data
- Payment failure (insufficient USDC balance) results in HTTP 402 response before data is returned
- Malformed path parameter may result in a 404 or upstream API error
- Rate limiting or quota exhaustion from the underlying Visual Crossing/RapidAPI provider
- Network timeout if the upstream RapidAPI service is slow or unavailable

## How this service works

21 paid weather API endpoints powered by x402 micropayments

## Output

Returns a JSON object with a 'data' field containing the Visual Crossing weather API response, including current conditions, forecasts, or historical weather depending on the path queried. Typical fields include temperature, weather conditions, humidity, wind speed, and timestamps.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "Location query (address, city, or coordinates)"
  },
  "location": {
   "type": "string",
   "description": "Location address 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-visual-crossing-proxy-b6fbc315/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)
