Back to Browse
x402 Weather API Hub – Dynamic Path Weather Endpoint
x402
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
Price / call$0.075
Success—
StatusUnknown
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.
Example use cases
Real-time city weather lookup
“Can you get me the current weather conditions for London, UK right now? I need temperature and general conditions.”
Coordinates-based weather fetch
“Fetch the weather data for coordinates 37.7749,-122.4194 — that's San Francisco — and tell me what conditions are like there.”
Travel planning weather check
“I'm planning a trip and need to know what the weather is like in Reykjavik, Iceland today. Can you pull that from the weather API?”
Technical details
Endpoint
POSThttps://x402-weather.vercel.app/api/weather338/%7Bpath%7D?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| queryrequired | string | Location query string |
| location | string | City name or coordinates |
Output
Schema · Response
| Field | Type | Description |
|---|---|---|
| data | object | Response data from the underlying RapidAPI provider |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"