# Apiosk Web Extraction Execute

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

Executes a web extraction operation via the Apiosk x402 pay-per-call gateway, extracting structured data from web pages using USDC micropayments on Base.

## Facts

- Endpoint: POST https://gateway.apiosk.com/web-extraction/execute
- Price: $0.07/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-web-extraction-execute-6ddd6e41
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zRVd8Ojnva9uUOyi5ObbY

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-web-extraction-execute-6ddd6e41 -d '<json body>'
```

Example prompt: Pull the main article text and metadata from https://example.com/article-page using the web-extraction operation so I can summarize it.

## When to prefer this

Choose this endpoint when you need to extract web content programmatically and are comfortable paying per-call in USDC via the x402 protocol on Base. It is ideal for agents that need lightweight, on-demand web extraction without managing scraping infrastructure, and suits use cases where cost-per-call economics are acceptable over subscription-based scrapers.

## Known failure modes

- Invalid or unreachable URL returns upstream_status 4xx or 5xx with an error result
- Unsupported operation id returns an error status
- Insufficient USDC balance triggers HTTP 402 payment required
- Malformed JSON input payload causes request rejection
- Target site blocking scraping returns empty or error result
- Network timeout results in high latency or failed status

## 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 (success/error), result (the upstream web extraction response body with extracted content), operation used, api identifier, cost in USDC, latency in milliseconds, and 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-web-extraction-execute-6ddd6e41/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)