# Apiosk Gateway – Scrapestack Execute

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

Executes a web scraping operation via the Scrapestack API through the Apiosk x402 pay-per-call gateway, forwarding the JSON payload and returning the upstream scraping result.

## Facts

- Endpoint: POST https://gateway.apiosk.com/scrapestack/execute
- Price: $0.11/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-scrapestack-execute-6c5d561c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vr2eiGs4GJpkwtraxwWsQ

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-scrapestack-execute-6c5d561c -d '<json body>'
```

Example prompt: Can you scrape the product listing page at https://example.com/products and return the full HTML content using the Scrapestack execute operation?

## When to prefer this

Choose this endpoint when you need to scrape web pages through Scrapestack's anti-bot and proxy infrastructure and want pay-per-call billing via USDC on Base (x402 protocol) without managing a Scrapestack subscription directly. Prefer this over direct Scrapestack API access when operating in an agent or crypto-native payment context where micropayments per call are preferred over monthly API key billing.

## Known failure modes

- Invalid or unreachable target URL causes upstream_status 4xx or 5xx with an empty or error result
- Missing or malformed operation selector causes gateway to return an error status
- Scrapestack rate limits or quota exhaustion returns upstream_status 429
- Payment failure (insufficient USDC balance) causes HTTP 402 before the request is forwarded
- Timeout on slow or heavy pages may result in high latency or a failed result

## 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 a status string, the upstream response body (the scraped content from Scrapestack), the HTTP status code returned by Scrapestack, the operation that was executed, the API slug, the cost of the call in USDC, and the latency in milliseconds.

## 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-scrapestack-execute-6c5d561c/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)