Back to Browse
Apiosk Gateway – OpenWeather Execute
x402
Apiosk Gateway – OpenWeather Execute is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.11/call, status down (last checked 2026-09-15).
Executes an OpenWeather API operation via the Apiosk x402 pay-per-call gateway, forwarding requests and returning upstream weather data responses.
Price / call$0.11
Success—
StatusDown
How this service works
Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on Base). This document covers the gateway's discovery and execution meta-endpoints. Individual provider APIs are reachable at /{api_slug}/{path} and described by GET /{api_slug}/metadata.
Output
Returns a JSON object containing the upstream OpenWeather API response body under 'result', along with metadata including the API slug, the operation called, HTTP status from the upstream, latency in milliseconds, cost of the call in USDC, and overall status string.
Example use cases
Real-time city weather lookup
“What's the current temperature, humidity, and weather description for Tokyo right now? Use the current weather operation.”
5-day forecast for travel planning
“I'm heading to Paris next week — can you pull the 5-day weather forecast from OpenWeather so I can see what to expect day by day?”
Air quality index check
“Can you check the current air quality index for Los Angeles using the OpenWeather air pollution endpoint? I want to know if it's safe to go for a run outside.”
Technical details
Endpoint
POSThttps://gateway.apiosk.com/openweather/executeWhen to prefer
Choose this endpoint when you need OpenWeather data without managing a separate OpenWeather API key, want micropayment-based pay-per-call billing in USDC via the x402 protocol, or are building an agent that needs weather data with transparent per-call cost accounting. Prefer WeatherAPI.com sibling endpoint if you need different data coverage or pricing.
Side effects
- Invalid operation selector returns error status with upstream_status non-200
- Malformed JSON payload in 'input' field causes upstream rejection
- Payment failure (insufficient USDC balance) blocks execution before upstream call
- Rate limiting or quota exhaustion on the OpenWeather upstream returns 429
- Unknown api_slug or misconfigured gateway route returns 404
- Network timeout to upstream returns high latency with error status
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| input | string | JSON payload forwarded to the selected operation. |
| operation | string | Operation id, /path, or METHOD /path selector. |
Output
Schema · Response
| Field | Type | Description |
|---|---|---|
| api | string | |
| cost | string | |
| resultrequired | — | Upstream response body. |
| statusrequired | string | |
| latency | number | |
| operation | string | |
| upstream_status | integer |
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"