# the402.ai Batch Web Scraper

> the402.ai Batch Web Scraper is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.003/call, status down (last checked 2026-09-15).

Purchases and initiates a batch web scraping job, returning a job ID and status for asynchronous tracking.

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_90347a57b7d64e57/purchase
- Price: $0.003/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-the402-ai-8dfb582e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AimCfmUDDej_TgQmGjwn7

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 api-the402-ai-8dfb582e -d '<json body>'
```

Example prompt: Start a batch web scraping job using the402.ai's Batch Web Scraper service — the service ID is svc_90347a57b7d64e57.

## When to prefer this

Choose this endpoint when you need to kick off a large-scale or multi-URL web scraping task asynchronously and want a job-tracking handle (job_id) in return. It is especially suited for workflows that require scraping many pages in a single batch rather than individual on-demand requests, and when using the x402 micropayment protocol at $0.003 USDC per call.

## Known failure modes

- Missing or invalid 'id' field returns a 400 validation error
- Unknown or inactive service ID results in a 404 not found
- Insufficient USDC balance or payment failure returns a 402 payment required error
- Service temporarily unavailable returns a 503 error
- Rate limiting may return a 429 too many requests error

## How this service works

Purchase: Batch Web Scraper

## Output

Returns a job_id to track the scraping job, a status string indicating the current job state, and a thread_id for correlating the async work. The agent can use the job_id with the platform's job-status endpoint to poll for completion.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id"
 ],
 "properties": {
  "id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "thread_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-the402-ai-8dfb582e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)
