Skip to main content
AdsCrawl is designed to be usable from your first request. This guide walks you from account creation to a working API call — no configuration files, no infrastructure setup, and no proxy accounts to manage separately. By the end, you’ll have a rendered page response in your terminal and a clear path to whichever API fits your use case.
1

Create a free account

Go to app.adscrawl.net/register and sign up. The Free plan gives you 500 credits with no credit card required — enough to explore HTML extraction, screenshots, and short CDP sessions.
2

Copy your API key

After signing in, open the AdsCrawl dashboard and copy your API key. Store it as an environment variable on your server or in a secret manager.
Never paste your API key into client-side JavaScript, commit it to source control, or include it in a public URL. Keep it on your server only.
3

Make your first request

Use POST /html to fetch a rendered page. This endpoint is synchronous — AdsCrawl launches a real browser, loads the URL, and streams the result back in the HTTP response.Set contentMode to control what you get back:
  • "html" — full rendered page HTML (default)
  • "markdown" — clean, readable Markdown extracted by the Readability parser
  • "json" — structured article object with title, byline, excerpt, and body
Use "waitUntil": "domcontentloaded" for most HTML and Markdown extraction — it’s faster and avoids waiting on analytics or lazy-loaded resources. Switch to "load" or "networkidle" when the content you need depends on secondary resources or deferred JavaScript.
4

Check the response

A successful request returns HTTP 200. The response body depends on contentMode:
If you receive a 402, your account is out of credits — check your balance in the dashboard. A 401 means the API key is missing or incorrect.

What to explore next

AdsCrawl has five APIs. Start with the one that fits your workflow:

Browser Tasks

HTML, Markdown, JSON, screenshots, and structured field extraction from SPAs.

Remote CDP

Connect Playwright or Puppeteer to a remote browser for scripted automation.

Cloud Browsers

Persistent browser profiles with a live viewer, saved cookies, and reusable state.

API Reference

Complete request and response schemas for every endpoint.
If you’d prefer to let your coding agent handle setup, paste this prompt into your agent:
The agent will walk you through sign-up and integration. You approve the API key request in your browser.
Once you’ve made your first successful request, read the Authentication page to understand the full credential model — especially if you plan to use Cloud Browsers or CDP sessions.