# the402.ai Web Page Scraper

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

Purchases and initiates a web page scraping job, returning a job ID and thread ID for async result retrieval

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_0d947adadb39492f/purchase
- Price: $0.005/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-b476530d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OZu-fgFXpYOvZeWXVB1Po

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-b476530d -d '<json body>'
```

Example prompt: Can you scrape the content of https://example.com/article for me and return the text — I want to extract the main body content from that page.

## When to prefer this

Use this endpoint when you need to programmatically scrape and extract content from a web page and are operating in a pay-per-use context using USDC micropayments. Prefer this over free scrapers when you need reliable, API-driven access with job tracking. Best for agents that need to fetch page content as part of a larger automated workflow and can poll for async results.

## Known failure modes

- Invalid or unreachable URL results in job failure status
- Insufficient USDC balance causes payment rejection and no job creation
- Target website blocks scraping (e.g. bot detection, CAPTCHA) resulting in failed job status
- Malformed request body returns 400 error
- Payment processing failure returns 402 error

## How this service works

Purchase: Web Page Scraper

## Output

Returns a JSON object containing a job_id (unique identifier for the scraping job), a status string (initial job state), and a thread_id (for tracking the async job thread). The agent should use the job_id to poll for results via the job status endpoint.

## 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-b476530d/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)