# Apiosk Gateway – Tavily Execute

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

Executes a Tavily web search or research operation via the Apiosk x402 pay-per-call gateway, returning the upstream Tavily response for a given search query or operation.

## Facts

- Endpoint: POST https://gateway.apiosk.com/tavily/execute
- Price: $0.0805/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-tavily-execute-e1c8b7cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UWLMp2lnxC8MFmetqxrxW

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-tavily-execute-e1c8b7cc -d '<json body>'
```

Example prompt: Search the web for the latest news about quantum computing breakthroughs in 2025 using Tavily's search operation — I need a summary of what's been found recently.

## When to prefer this

Choose this endpoint when you need Tavily's AI-powered web search or research capabilities and want to pay per call in USDC via the x402 protocol without managing a separate Tavily API key or subscription. Ideal for agents making occasional or unpredictable search calls that benefit from a metered, crypto-native payment model.

## Known failure modes

- Invalid or unrecognized operation selector returns an error status
- Malformed JSON payload in the input field causes upstream rejection
- Insufficient USDC balance or failed x402 payment prevents execution
- Tavily upstream service unavailable returns a non-200 upstream_status
- Rate limiting or quota exceeded on the Tavily provider side

## 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 status, the upstream Tavily response body (search results, summaries, or other operation output), the operation invoked, latency in milliseconds, and the cost charged in USDC.

## 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-tavily-execute-e1c8b7cc/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)