Set it up yourself
- Sign up for an AdsCrawl account.
- Copy your API key from the dashboard.
- Choose an API example and send your first request.
When scraping gets tough, send in a real browser
Connect Playwright, Puppeteer or CDP to real cloud browsers. Extract HTML, Markdown, JSON and screenshots with residential proxy routing.
AdsCrawl is a managed cloud browser and browser automation API for developers. Connect Playwright, Puppeteer or a CDP client to cloud Chromium, use supported residential proxy routing or your own proxy, and retrieve HTML, Markdown, JSON or screenshots from dynamic websites. For browser context that spans multiple tasks, use the separate Cloud Browser API to save and reuse profiles; login validity remains subject to the target website.
Five APIs cover rendered pages, structured data, screenshots, and live browser control. Pick a workflow and send your first request in minutes.
curl --fail-with-body -sS \
-X POST "https://api.adscrawl.net/html" \
-H "x-api-key: $ADSCRAWL_API_KEY" \
-H "content-type: application/json" \
-d '{
"url": "https://www.adscrawl.net",
"contentMode": "html",
"waitUntil": "domcontentloaded"
}' \
--output page.html
# Use "contentMode": "markdown" for readable text.Route each browser through the region you need, with fewer failures from geo restrictions, IP conflicts, or unavailable proxy nodes.
Skip the proxy pool and the rotation logic.
Grab an API key and set it up yourself, or have your coding agent handle the integration.
Paste one prompt into your coding agent. It will walk you through sign-up, request access to an API key, and integrate AdsCrawl into your project. You approve access in your browser.
Set up AdsCrawl in this codebase. Use https://api.adscrawl.net/auth.md to help me create an account and authorize an API key, then follow https://api.adscrawl.net/docs/agent-quickstart.md to complete the integration.ADSCRAWL PRODUCTS
From a single page request to a reusable browser profile. Explore the use cases, integration steps and limits of each workflow.
Run your Puppeteer workflow against cloud Chromium. Your Node.js application controls navigation and extraction while AdsCrawl hosts the browser session.
Explore productCreate a cloud Chromium session and connect your CDP client. Keep browser provisioning, protocol access and cleanup in one explicit lifecycle.
Explore productReturn to an authorized account workflow with a saved browser profile. Inspect the login state, complete any required sign-in and stop the runtime when finished.
Explore productConnect your agent's tool layer to a real cloud browser. Your application chooses the model and action policy; AdsCrawl supplies the browser session.
Explore productSave a browser profile, launch it with your proxy, and pick up the workflow in a live viewer. Stop the runtime when you are done; keep the profile for later.
Explore productRender JavaScript pages in a browser and extract a defined set of fields. Give your pipeline structured results instead of another page to parse.
Explore productKeep browser logic in your Node.js application. Connect over CDP to navigate pages, fill forms and collect results in a temporary remote session.
Explore productTurn a URL into a PNG. Capture the whole page or focus on one element, then save the result alongside your workflow's data.
Explore productGet the article content your text pipeline needs. Render the page, request Markdown and preserve its source for the next step.
Explore productPower your next feature with a real browser—from a single page request to a multi-step workflow.
Explore the API docsHTML · Scrape · Screenshots
Fetch rendered HTML, pull structured fields from dynamic pages, and capture screenshots for research, monitoring, or AI workflows.
Read web scraping docsCAPTCHA Solver · 2Captcha
Detect and handle supported challenges such as reCAPTCHA, Turnstile, and AWS WAF in the same browser session—without a manual handoff.
Read browser task docsCDP · Playwright
Connect Playwright to a remote browser to navigate, click, fill out forms, and collect results—all in one session.
Read Remote CDP docsCloud Browser
Launch a Cloud Browser with your proxy and cookies, use it in the live viewer, then stop the session and reuse the saved profile later.
Read Cloud Browser docsPractical guides and side-by-side tool comparisons for web scraping and browser automation.
Browse all articlesCustomer reviews and published security certifications

E-commerce
I chose AdsPower to manage my accounts securely, and I've been happy with it so far.
View original review
Freelancer
I like the browser fingerprint protection, and the pricing is competitive.
View original review
Business Development Manager
I use AdsPower for affiliate marketing, especially its RPA tools for automating repetitive work.
View original review
Audited security controls

Information security management

Privacy information management
Reviews are excerpted or summarized from AdsPower's website.
Everything you need to make your first request and choose the right browser workflow.
Create an account, copy your API key from the dashboard, and run one of the examples above. Send the key in the x-api-key header, and keep it on your server.
Use HTML for rendered content, Scrape for structured fields, and Screenshots for page images. Use CDP when you need scripted interaction, or Cloud Browser when you want a reusable profile and a live viewer.
Yes. AdsCrawl renders the page in a browser before returning the result. Where supported, set waitUntil or wait for a selector so the content you need has time to load.
Yes. Set contentMode to markdown on POST /html for clean, readable content. Use html for rendered markup or json for a structured version of the article.
Call POST /spa-extract with mode set to extract, then define the fields you need. DOM fields use CSS selectors, while network fields can read matching JSON responses. Check missingFields in the response to see what was not found.
Yes. POST /screenshot returns a PNG. Set fullPage for the entire page, or pass a selector to capture the first matching element. Save the response as a binary file.
Yes. The HTTP APIs work with Node.js fetch, Python requests, cURL, and other HTTP clients. For browser automation, create a CDP session and connect Playwright with the returned webSocketDebuggerUrl.
CDP gives your automation a temporary remote browser session. Cloud Browser saves the browser profile and includes a live viewer while it is running. Stop it when you're done; the profile will be ready for your next run.
Yes. APIs that support proxies accept a custom configuration. Every Cloud Browser launch request must include a valid proxy. Put the credentials in the designated fields, not in the proxy server URL.
Yes. Supported tasks and Cloud Browser workflows accept cookies. Use cookies only for accounts you are authorized to access, and check the domain, path, and expiration. For multi-step sign-in flows, use a CDP session.
No. Closing the viewer leaves the Cloud Browser running, so usage charges continue. Call the stop endpoint and confirm that runtime.status is stopped. To release a temporary CDP session, call DELETE /cdp/sessions/:sessionId.
The page may be slow, the proxy may be unreachable, or the selector you are waiting for may never appear. Check the error response, verify the URL and proxy, then adjust the wait condition or timeout within the endpoint's documented limits.
If you get HTTP 402, check your credit balance and plan in the dashboard. For HTTP 429, lower your concurrency and retry with backoff. You can find current plan limits on the pricing page and in your account.
Yes. Copy the setup prompt above into your coding agent. It will guide you through sign-up and integration. Approve the API key request in your browser, then let the agent finish the setup.
Still have questions? View API docsPricing