# the402.ai Web Crawler Purchase

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

Initiates a paid web crawling job on the the402.ai platform, returning a job ID and status for async tracking

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_ed1c6e81e8ec4ea0/purchase
- Price: $0.263/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-5282e6b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Coes3Nu9o1MlojKjDlenn

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

Example prompt: Kick off a web crawl job on the402.ai using service ID svc_ed1c6e81e8ec4ea0 — I need to extract content from a site and I want to get back the job ID so I can check on it later.

## When to prefer this

Choose this endpoint when you need to programmatically initiate a web crawl through a pay-per-use micropayment API (x402/USDC), and you require an async job-based workflow where results are retrieved later via job ID. Prefer this over synchronous scrapers when the target content may take time to fetch or when you want a managed, auditable crawl pipeline on the402.ai platform.

## Known failure modes

- Missing or invalid 'id' field returns a 400 validation error
- Unknown or unauthorized service ID returns a 403 or 404
- Insufficient payment or x402 payment failure blocks job creation
- Platform overload or downtime returns a 503
- Job creation succeeds but crawl fails asynchronously — must be detected via job status endpoint

## How this service works

Purchase: Web Crawler

## Output

Returns a JSON object with a job_id (unique identifier for the crawl job), status (current state of the job, e.g. pending/running), and thread_id (for tracking the async execution thread on the402.ai platform).

## 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-5282e6b8/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)