# Apiosk Gateway – Jina Reader Execute

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

Executes a Jina Reader API operation via the Apiosk pay-per-call gateway, forwarding a JSON payload to Jina Reader and returning the upstream response, billed at $0.06 USDC per call over the x402 protocol.

## Facts

- Endpoint: POST https://gateway.apiosk.com/jina-reader/execute
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-jina-reader-execute-903db2bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1atRKz2jjr9fZ1q3tQYuy

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-jina-reader-execute-903db2bc -d '<json body>'
```

Example prompt: Use Jina Reader to fetch and extract the clean readable text from https://example.com/some-article so I can summarize it.

## When to prefer this

Choose this endpoint when you need to extract clean, readable text or markdown from a URL using Jina Reader's parsing quality, and you want pay-per-call billing in USDC without managing a Jina API key directly. Prefer it over raw Jina Reader when working in an x402-compatible agent pipeline that handles micropayments automatically.

## Known failure modes

- Invalid or unreachable URL causes upstream 4xx/5xx error reflected in upstream_status
- Malformed JSON payload in 'input' field causes forwarding failure
- Unknown or misspelled operation selector returns error
- Insufficient USDC balance or failed x402 payment prevents call execution
- Rate limiting or quota exhaustion from upstream Jina Reader API

## 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 a status string, the upstream Jina Reader response body (result), the operation executed, the API slug, call latency in milliseconds, cost string, 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-jina-reader-execute-903db2bc/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)