# Apiosk Gateway – Serper Execute

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

Executes a Serper (Google Search API) operation via the Apiosk x402 pay-per-call gateway, forwarding a JSON payload to the selected Serper endpoint and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/serper/execute
- Price: $0.15/call
- Payment: x402
- Status: down
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-serper-execute-f8860f90
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bAJ-0-2UcM7qvhn5dRZ6l

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-serper-execute-f8860f90 -d '<json body>'
```

Example prompt: Search Google for 'best open-source LLMs in 2025' using Serper through Apiosk and give me the top organic results — use the search operation.

## When to prefer this

Choose this endpoint when you need programmatic access to Google Search results (via Serper) and are operating in an x402/USDC micropayment environment on Base, or when you want to avoid managing Serper API keys directly. Prefer this over direct Serper API calls when your agent stack already handles x402 payments or when you want a unified gateway for multiple APIs under one protocol.

## Known failure modes

- Invalid operation selector returns an error status with no result
- Malformed JSON in the input field causes upstream rejection
- Insufficient USDC balance triggers an HTTP 402 payment-required error
- Serper upstream rate limit or outage returns a non-200 upstream_status
- Missing required input fields result in a gateway validation 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 containing: status (success/error string), result (the raw upstream Serper/Google Search API response body with organic results, snippets, and metadata), api (the API slug), operation (the operation used), cost (USDC amount charged), latency (milliseconds), and upstream_status (HTTP status code from Serper).

## 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-serper-execute-f8860f90/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)