# Bytemine Crawl Continue

> Bytemine Crawl Continue is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).

Resumes processing of pending pages in an existing crawl job, meant to be called repeatedly until the job status returns 'completed'.

## Facts

- Endpoint: POST https://x402.orthogonal.com/bytemine/crawl/continue
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bytemine-crawl-continue-af01743f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ADxCBVhmmNojKxTlE_EKA

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 bytemine-crawl-continue-af01743f -d '<json body>'
```

Example prompt: Keep advancing my Bytemine crawl job with ID 'job_abc123' — call continue on it repeatedly until the status comes back as completed.

## When to prefer this

Use this endpoint after initiating a crawl job with a separate start/create endpoint when the crawl has more pages than can be processed in a single call. This is the continuation step in a multi-call crawl workflow. Prefer this over starting a new crawl if you already have an active job_id with pending pages remaining.

## Known failure modes

- Invalid or unknown job_id returns an error indicating the job was not found
- Job already completed returns a completed status without additional processing
- Payment failure (insufficient USDC balance) prevents the call from being made
- Network timeout may occur for large crawl jobs with many pending pages
- Rate limiting may temporarily block repeated rapid calls

## How this service works

Resume processing pending pages in an existing crawl job. Call repeatedly until status is 'completed'.

## Output

Returns the current status and progress of the crawl job, including any newly processed page data. The agent should check the 'status' field and keep calling this endpoint until it reads 'completed'.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string",
   "description": "Crawl job ID to continue"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bytemine-crawl-continue-af01743f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)