# httpay.xyz NWS Weather API Gateway

> httpay.xyz NWS Weather API Gateway is a paid API for AI agents from httpay.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Proxies requests to the US National Weather Service (NWS) API via a pay-per-call x402 gateway requiring 0.001 USDC per request

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/weather/%7B*path%7D
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-nws-weather-api-gateway-3454b644
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tPMwaE7PGfFq90f_TIrUv

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 httpay-xyz-nws-weather-api-gateway-3454b644 -d '<json body>'
```

Example prompt: What's the 7-day weather forecast for Denver, Colorado? Use the NWS API to get the gridpoint forecast for lat 39.7392, lon -104.9903.

## When to prefer this

Use this endpoint when you need programmatic access to NWS weather data (forecasts, alerts, observations) and want to pay per-call via x402/USDC without managing NWS API keys or your own proxy. Prefer over direct NWS API calls when operating in an agent context with x402 payment rails already set up. NWS data is free at source, so this is primarily valuable for the payment-gated proxy convenience in automated/agent workflows.

## Known failure modes

- NWS API path not found — returns 404 if the gridpoint or station ID is invalid
- Location outside the US — NWS only covers US territories; non-US coordinates return 404 or empty
- Payment not included or insufficient — x402 gateway rejects request without valid USDC payment
- NWS upstream outage — NWS occasionally has maintenance windows causing 503 errors
- Malformed path — incorrect NWS API path structure returns 400 or routing error
- Rate limiting — NWS imposes its own rate limits that may propagate as 429 errors

## How this service works

API Gateway: US Weather (NWS) API

## Output

Returns the NWS API JSON response for the requested path — which may include forecast periods (name, temperature, wind, short/detailed forecast), weather alerts (event, severity, area), current observations, or gridpoint metadata depending on the path queried.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-nws-weather-api-gateway-3454b644/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from httpay.xyz](https://www.zero.xyz/host/httpay.xyz/llms.txt)