# Apiosk Gateway – WeatherAPI.com Execute

> Apiosk Gateway – WeatherAPI.com Execute is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.155/call, status down (last checked 2026-09-15).

Executes a pay-per-call WeatherAPI.com operation via the x402 HTTP 402 / USDC-on-Base payment protocol, forwarding the request and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/weatherapi/execute
- Price: $0.155/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-weatherapi-com-execute-6027d9ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kj6ybdqqoiwOlkkYSXcEI

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-weatherapi-com-execute-6027d9ad -d '<json body>'
```

Example prompt: What's the current weather in London right now — temperature, humidity, and wind speed? Use the WeatherAPI current.json operation with London as the query.

## When to prefer this

Choose this endpoint when you need programmatic, pay-per-call access to WeatherAPI.com data without managing an API key subscription, especially in x402-compatible agent workflows that handle USDC micropayments on Base. Prefer it over direct WeatherAPI.com integration when you want zero-setup billing or are orchestrating multiple API providers through the same gateway.

## Known failure modes

- Invalid operation selector returns an error from the gateway
- Malformed JSON payload causes upstream rejection
- Insufficient USDC balance triggers HTTP 402 payment failure
- Unknown location query returns a WeatherAPI 'No matching location found' error
- Rate limits or quota exhaustion on the underlying WeatherAPI.com key
- Network timeout from upstream WeatherAPI.com returns elevated latency or gateway error

## 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 with a status string, the upstream WeatherAPI.com response body (current conditions, forecast, AQI, etc.), the operation echoed back, the latency in milliseconds, the cost of the call in USDC, and the upstream HTTP status code.

## 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-weatherapi-com-execute-6027d9ad/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)