# Apiosk Gateway - Attestations Execute

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

Executes a pay-per-call API operation through the Apiosk x402 gateway, routing the request to the selected upstream provider and returning the response with metadata.

## Facts

- Endpoint: POST https://gateway.apiosk.com/attestations/execute
- Price: $0.02/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-attestations-execute-f6ea6e3f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hF0iNzivX6Xx2Slg2V7PE

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-attestations-execute-f6ea6e3f -d '<json body>'
```

Example prompt: Run the 'GET /current' operation on the open-meteo API through Apiosk's gateway, passing in this JSON payload: {"latitude":48.85,"longitude":2.35} — and tell me the result along with what it cost.

## When to prefer this

Choose this endpoint when you need to call one of Apiosk's proxied upstream APIs (e.g. Open-Meteo, Mapbox, Aviationstack, Twelve Data, OpenWeather, financial-identifiers) via a single unified pay-per-call interface using USDC on Base, rather than integrating each provider's API key and billing separately. Ideal for agents that need metered, blockchain-settled API access without managing multiple provider accounts.

## Known failure modes

- Invalid or unrecognized operation selector returns an error status
- Malformed JSON in the input field causes upstream rejection
- Insufficient USDC balance or x402 payment failure blocks the call
- Upstream provider is unavailable, returning a non-200 upstream_status
- Missing required fields (operation or input) results in a gateway-level error
- Rate limiting by the upstream API propagated back through the gateway

## 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 API response body under 'result', a 'status' string, the 'latency' in milliseconds, 'cost' as a string (e.g. USDC amount), the 'operation' that was called, the 'api' slug, and 'upstream_status' as an integer HTTP 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-attestations-execute-f6ea6e3f/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)