# Apiosk Gateway – Exa Execute

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

Executes an Exa API operation via the x402 pay-per-call gateway, forwarding a JSON payload to the selected Exa endpoint and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/exa/execute
- Price: $0.115/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-exa-execute-11cffa47
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EDQEfKiDvwJjxSKeSkpsk

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-exa-execute-11cffa47 -d '<json body>'
```

Example prompt: Search Exa for the most relevant recent articles about 'AI agents in production' — use the search operation and return the top results.

## When to prefer this

Use this endpoint when you need to call Exa's search API without a direct Exa API key, want pay-per-call billing in USDC via x402, or are building an agent that uses the Apiosk gateway ecosystem for unified API access.

## Known failure modes

- Payment not included or insufficient — HTTP 402 returned before forwarding
- Invalid operation selector — gateway cannot resolve the Exa path
- Malformed JSON in the input field — upstream returns 400
- Exa API is unavailable — upstream_status reflects 5xx error
- Rate limit exceeded on upstream Exa API — returns upstream 429

## 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 status, the upstream Exa response body under 'result', the operation used, cost in USDC, latency in milliseconds, 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-exa-execute-11cffa47/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)