# Scrapling x402 Batch Scrape

> Scrapling x402 Batch Scrape is a paid API for AI agents from scraplingdata.xyz, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-22).

Batch-scrapes multiple URLs and returns structured page data (title, tables, JSON-LD, markdown) with a content hash for provenance, paid per-call via x402 micropayments.

## Facts

- Endpoint: POST https://scraplingdata.xyz/v1/batch-scrape?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scrapling-x402-batch-scrape-e15019ac
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__G-tOh5W2nG5Jdjc5ZPto

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 scrapling-x402-batch-scrape-e15019ac -d '<json body>'
```

Example prompt: Can you scrape these three URLs for me — https://example.com, https://news.ycombinator.com, and https://openai.com — and give me back the title, markdown content, any tables, and a provenance hash for each page?

## When to prefer this

Choose this endpoint when you need to extract structured content (markdown, tables, JSON-LD) from multiple URLs in a single API call with built-in provenance verification via SHA-256 hashes. It is well-suited for AI agent pipelines that require verifiable, auditable web data. The per-call micropayment model via x402 makes it practical for variable-volume workloads without subscription overhead.

## Known failure modes

- URL is unreachable or returns non-200 status — reflected in per-result status field
- Anti-bot protection blocks scrape — may return empty or partial data with lower quality score
- Invalid URL format in batch — likely causes individual result failure or error
- Payment not settled via x402 — request rejected before scraping begins
- Rate limiting or overload — request may time out or return partial batch results

## How this service works

Autonomous AI Agent (HTTP 402 / x402 v2 / MCP) & O: Drive Data Seller Gateway. All payments settle to 0x72C80C01fD89Bac74f47cf604b61ACd119c9BCdb.

## Output

A JSON object containing a count of results and an array where each entry includes the original URL, extracted data (title, tables, JSON-LD, markdown), HTTP status code, scrape tier used, a SHA-256 provenance hash of the fetched page, and a quality score (0–100).

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 2,
  "results": [
   {
    "url": "https://example.com",
    "data": {
     "title": "Example Domain",
     "tables": [],
     "json_ld": [],
     "markdown": "# Example Domain ..."
    },
    "status": 200,
    "tier_used": "static_scrape",
    "provenance": {
     "sha256": "<sha256 of fetched page>"
    },
    "quality_score": 90
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scrapling-x402-batch-scrape-e15019ac/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from scraplingdata.xyz](https://www.zero.xyz/host/scraplingdata.xyz/llms.txt)