# Apiosk Gateway – OpenWeather Execute

> 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.

## Facts

- Endpoint: POST https://gateway.apiosk.com/openweather/execute
- Price: $0.11/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-openweather-execute-1a636ffc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sMXmN1wDLAeVEB3DO84WB

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 apiosk-gateway-openweather-execute-1a636ffc -d '<json body>'
```

Example prompt: Can you get the current weather conditions for London right now — temperature, humidity, and wind speed — using the OpenWeather current weather operation?

## When to prefer this

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.

## Known failure modes

- 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

## 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.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "JSON payload forwarded to the selected operation."
  },
  "operation": {
   "type": "string",
   "description": "Operation id, /path, or METHOD /path selector."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "status",
  "result"
 ],
 "properties": {
  "api": {
   "type": "string"
  },
  "cost": {
   "type": "string"
  },
  "result": {
   "description": "Upstream response body."
  },
  "status": {
   "type": "string"
  },
  "latency": {
   "type": "number"
  },
  "operation": {
   "type": "string"
  },
  "upstream_status": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiosk-gateway-openweather-execute-1a636ffc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.apiosk.com](https://www.zero.xyz/host/gateway.apiosk.com/llms.txt)