Web Scraper API

One synchronous call fetches a page and returns it as HTML, visible text, markdown, or the exact fields you asked for. JavaScript rendering and anti-bot bypass are handled for you, so a single request replaces a headless browser plus a proxy stack.

The Web Scraper API is a single endpoint: POST https://api.capzy.ai/scrape. Authentication is your clientKey in the JSON body, the same key that runs the Solver API and draws from one account balance. In the common case the response comes back on the same request. Long jobs fall back to a taskId you poll.

Render on demand

Set renderJs to run a real headless browser for JS-heavy sites, then wait on a selector or script scenario.

Anti-bot bypass

Turn on asp to auto-detect and clear Cloudflare, DataDome, PerimeterX, Akamai, Imperva, and AWS WAF over residential egress.

Built-in extraction

Pass extractionRules with CSS or XPath selectors and get a clean JSON object back instead of raw HTML.

A first request

The only required fields are clientKey and url. Everything else has a default. This fetches a page over datacenter egress and returns it as markdown.

scrape.sh

curl -s https://api.capzy.ai/scrape \
  -H 'Content-Type: application/json' \
  -d '{
    "clientKey": "capzy_YOUR_KEY",
    "url": "https://example.com",
    "format": "markdown"
  }'
# -> { "errorId": 0, "status": "ready", "result": { "content": "# Example...", "format": "markdown", ... } }

One key, one balance

Create your clientKey once in the dashboard. Failed requests are free, and cache hits cost zero, so you can iterate on selectors without spending balance.

Where to go next

Making a request covers the full request and response shape, the core parameters, and the synchronous-versus-polling behavior.
Rendering & anti-bot covers renderJs, wait conditions, script scenarios, screenshots, and asp.
Extraction & formats covers format and extractionRules.
Pricing explains the feature-additive cost model, and Errors lists every error code.

Making a request