Documentation
Browser Crawl Engine renders web pages in a real Chrome browser and gives you the resulting HTML over HTTPS. You choose the URLs and the exit country; we handle the browser, the egress, block detection and retries.
The model in one paragraph
You submit a job containing between 1 and 1,000 URLs.
Each URL becomes an independent task. Tasks are claimed
by workers, rendered, and stored. You poll the job for counters and
per-task status, then download each task's HTML. Nothing about this is
synchronous: POST /v1/jobs returns as soon as the work is
durably recorded, usually in well under a second.
Base URL and format
Every endpoint lives under /v1. Requests and responses are
JSON, except HTML downloads. Successful responses carry
"ok": true; failures carry "ok": false and a
human-readable error.
{"ok": false, "error": "Human-readable message"}Endpoints at a glance
| Endpoint | Scope | Purpose |
|---|---|---|
POST /v1/jobs | jobs:create | Submit up to 1,000 URLs |
GET /v1/jobs/{jobId} | jobs:read | Counters and task list |
GET /v1/tasks/{taskId} | jobs:read | One task's metadata |
GET /v1/tasks/{taskId}/html | results:read | Download rendered HTML |
GET /v1/me | any valid key | Who this key belongs to |
GET /v1/me/balance | any valid key | Your current balance |
GET /v1/me/audit | audit:read | Your own API activity |
GET /healthz | none | Readiness probe |
Your responsibilities
You must have the right to collect the pages you request. We are infrastructure: we do not evaluate whether a target permits automated access, and submitting a URL is your assertion that you may collect it.
We respond to complaints from site operators by blocking the target for the account involved, and repeat offences end the account. Robots directives, terms of service and applicable law are yours to observe.
What the service does not do
- No CAPTCHA solving.
- No browser fingerprint spoofing or anti-detection tooling.
- No residential proxy network built from consumer devices.
- No data extraction — you get HTML, and parsing is yours.
A site that actively refuses automated traffic will keep refusing it, and the API will report that honestly rather than storing a challenge page as a success.