# Apiosk Gateway – Open-Meteo Execute

> Apiosk Gateway – Open-Meteo Execute is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-16).

Executes Open-Meteo weather API operations via a pay-per-call x402/USDC gateway, forwarding JSON payloads to the upstream Open-Meteo service and returning the response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/open-meteo/execute
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-open-meteo-execute-11fb7e4c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j15mab6A-WUWjfhs3olvZ

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-open-meteo-execute-11fb7e4c -d '<json body>'
```

Example prompt: Can you fetch the 7-day hourly weather forecast for latitude 48.8566, longitude 2.3522 (Paris) including temperature and precipitation probability using the Open-Meteo operation GET /v1/forecast?

## When to prefer this

Prefer this endpoint when you need Open-Meteo weather data without managing an Open-Meteo API key or subscription, want pay-per-call billing in USDC on Base, or are operating in an x402-compatible agent environment. Ideal for low-volume or one-off weather lookups where paying per call is more economical than a subscription. Choose this over direct Open-Meteo access when you want a unified gateway billing model or when your agent already handles x402 payments.

## Known failure modes

- Invalid operation selector returns an error indicating the operation was not found
- Malformed JSON input payload causes upstream 400 or validation error
- Payment not completed (402) results in no execution and a payment-required response
- Upstream Open-Meteo service outage returns a non-200 upstream_status with an error in result
- Out-of-range coordinates or unsupported weather variable returns an upstream API error
- Exceeding request rate limits may return throttling errors

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

A JSON object containing a status string, the upstream Open-Meteo response body (forecast data, current conditions, or historical data depending on the operation), the operation used, the API slug, the cost of the call, and the latency in milliseconds. The result field mirrors the Open-Meteo API response structure with fields like temperature, wind speed, precipitation, and hourly/daily arrays.

## 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-open-meteo-execute-11fb7e4c/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)