# Apiosk Gateway – Firecrawl Execute

> Apiosk Gateway – Firecrawl 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 Firecrawl web-crawling/scraping operation via the Apiosk x402 pay-per-call gateway, forwarding the JSON payload to the Firecrawl API and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/firecrawl/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-firecrawl-execute-62db076b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LkeR4xW_dLtpAT91RdzPT

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-firecrawl-execute-62db076b -d '<json body>'
```

Example prompt: Scrape the content of https://example.com/article using Firecrawl — use the scrape operation and pass that URL as the input so I can read the full text of the page.

## When to prefer this

Choose this endpoint when you need to scrape or crawl web pages using Firecrawl's capabilities but want to pay per-call in USDC via the x402 protocol without managing a separate Firecrawl API key or subscription. Ideal for sporadic or agent-driven scraping tasks where micropayment-based access is preferred.

## Known failure modes

- Invalid or unsupported operation ID returns an error status
- Malformed JSON input payload causes upstream rejection
- Target URL is unreachable or blocked, returning a non-200 upstream_status
- Payment not attached or insufficient USDC balance causes 402 rejection at the gateway
- Firecrawl rate limits or timeouts result in latency spikes or error responses
- Unknown api_slug routing causes 404 at gateway level

## 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 Firecrawl response body (scraped/crawled content), the operation used, latency in milliseconds, cost of the call, 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-firecrawl-execute-62db076b/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)