Create state you can inspect
Create a test profile and record its ID. Start it with a valid proxy. In the viewer, open a site you are authorized to test and sign into a test account or save a recognizable cookie.
Cloud Browser API
Create, start and stop saved browser profiles through an API. Run a full AdsPower fingerprint browser with your proxy, open its live viewer, and reuse cookies and settings for your next task.
01 / OVERVIEW
AdsCrawl Cloud Browser API manages persistent browser profiles in isolated cloud environments hosted by AdsCrawl. Create a profile, start it with your proxy, query its status and stop it after use. Each profile runs a full AdsPower anti-detect browser with native fingerprints and browser updates that follow AdsPower. Saved settings, cookies and tab snapshots let you reuse the same profile across tasks. Sign in to open the interactive viewer and control the browser through WebRTC.
Remote CDP Browser: Choose a temporary Chromium session for scripted automation when you do not need a saved profile.
Authenticated Web Scraping: Plan login checks, account isolation and profile reuse for content that requires a signed-in account.
Compare AdsCrawl and Browserbase for saved state, CDP and runtime costs →
PRODUCT RECORDING · 1:41
A full AdsPower fingerprint browser, running in an isolated cloud environment self-hosted by AdsCrawl. Open it from your browser and take your testing, private browsing and everyday work beyond a single device.
A real-time video stream keeps clicking, typing, scrolling and switching tabs feeling natural, much like using a local browser.
Browse websites, run web apps and install browser extensions. Test, research and get everyday work done in a familiar workspace.
Keep your profile and cookies, then sign in to AdsCrawl from another device to return to the same environment with less setup.
Powered by AdsPower's native fingerprint browser, with updates that follow AdsPower. Separate browser state gives each workflow its own space.
VALIDATE ONE COMPLETE TASK
Create a test profile and record its ID. Start it with a valid proxy. In the viewer, open a site you are authorized to test and sign into a test account or save a recognizable cookie.
Call stop and confirm the runtime has ended. Keep the profile, then start the same profile ID with a valid proxy. Closing the viewer alone does not stop billing.
Check whether the test cookie remains and whether the account page is still signed in. Retaining a cookie does not guarantee a permanent login: server expiration, revocation or revalidation can require a new sign-in.
This is a reproducible acceptance procedure, not a newly measured login-retention result. It checks persistent Cloud Browser profiles; temporary Remote CDP sessions use a separate lifecycle.
02 / USE CASES
Keep the profile id and start the same environment for your next task. Saved cookies and tab snapshots help you resume account workflows, subject to each website's login and session policies.
Use the API to create profiles, start them with your proxy, check runtime status and stop them between tasks. Keep separate profiles for different accounts or test environments.
Sign in to the live viewer to complete a login, inspect a page or test a web application. Interact through WebRTC and install browser extensions in a full AdsPower fingerprint browser.
03 / QUICKSTART
Requires Bash, cURL and jq. Set the ADSCRAWL_API_KEY environment variable on your server first.
Full request and response reference →# Replace the proxy address with your own proxy.
curl --fail-with-body -sS --max-time 200 \
-X POST "https://api.adscrawl.net/cloud-browsers/launch" \
-H "x-api-key: $ADSCRAWL_API_KEY" \
-H "content-type: application/json" \
-d '{
"proxy": { "server": "http://proxy.example.com:8080" },
"tabs": ["https://www.adscrawl.net"]
}'
# Open runtime.connectUrl from the response.
# When finished, replace <browser-id> with the returned id.
curl --fail-with-body -sS -X POST \
"https://api.adscrawl.net/cloud-browsers/<browser-id>/stop" \
-H "x-api-key: $ADSCRAWL_API_KEY"
# Requires jq. Replace <browser-id> with the same id used above.
# A successful stop request can still return status "stopping".
BROWSER_ID="<browser-id>"
stopped=false
for ((attempt=0; attempt<60; attempt++)); do
detail=$(curl --fail-with-body -sS --max-time 30 \
"https://api.adscrawl.net/cloud-browsers/$BROWSER_ID" \
-H "x-api-key: $ADSCRAWL_API_KEY") || exit 1
status=$(printf '%s' "$detail" | jq -er '.runtime.status') || exit 1
if [ "$status" = "stopped" ]; then
stopped=true
break
fi
sleep 2
done
if [ "$stopped" != true ]; then
printf '%s\n' 'Shutdown is not confirmed. Check this profile; do not launch a replacement.' >&2
exit 1
fi
# Closing the viewer does not stop billing.
# If launch fails, inspect its returned id; do not repeat launch.WORKFLOW GUIDE
Choose Cloud Browser API for a saved profile you can stop and reuse. Choose Remote CDP for a temporary scripted session, or Web Scraping API for a single page's fields. Each workflow has its own API and cleanup step.
Use a saved Cloud Browser profile when you need to return to its browser context. Retain the profile id, stop the runtime between tasks, and start that same profile for the next run. Each launch call creates a new profile.
Follow the saved-profile lifecycleUse Remote CDP when a Playwright or Puppeteer script needs a temporary browser. Create a CDP session, connect your client, and release the session in your cleanup step.
Explore temporary CDP sessionsUse the Web Scraping API when your task is to retrieve named fields from a dynamic page. Define the fields and inspect the result without managing a reusable Cloud Browser profile.
Explore structured extraction04 / LIMITS & BILLING
Sign up with 500 one-time credits. Hobby is $9/month, Starter $49/month and Pro $199/month. Launching a persistent Cloud Browser requires a paid plan.
Compare plans and allowances →Keep API keys on the server. For HTTP 402 check your balance; for 429 reduce concurrency and retry with backoff.
05 / FAQ
Use Cloud Browser API when you need a saved browser profile that you can stop and start again with its cookies and settings. Use Remote CDP for a temporary Playwright or Puppeteer session with a separate create, connect and delete lifecycle. Cloud Browser's interactive viewer requires a login session.
A stopped profile does not occupy a running slot. It still counts toward saved profile capacity. Stop a running browser explicitly after use.
No. Profile reuse does not override the target website's cookie expiration, sign-in policy or session revocation. Check the current state before running a task.
Viewer access requires a login session. Keep API keys on your server and use the documented authentication for each endpoint.
Yes. The full browser supports installing extensions for your workflow, alongside browsing websites and running web applications.
WebRTC streams the interactive browser view in real time, supporting responsive scrolling, typing and everyday browsing. Actual responsiveness depends on your connection and the running environment.