Can AdsPower stay installed?

Yes, but not on the same port. Both answer on 127.0.0.1:50325, and only one program can hold a port. Close AdsPower while your scripts run here, or give Scalebrowser another port in the same config line and point the script there.

Why is the AdsPower API off by default?

Sites can probe local ports. Some sites check which ports answer on your PC, and 50325 is the one AdsPower uses. It stays closed until you need it, and you can close it again once your scripts use the native API.

Does the AdsPower API need a token?

No, as with AdsPower. It answers any program on this PC and nothing outside it. The REST API, the SDKs and MCP on 127.0.0.1:8787 ask for a bearer token.

What if a script needs more than the 14 calls?

Use the native API beside it. The REST API, the Python and Node SDKs and MCP reach the same profiles on the same PC, so a script can move over one call at a time. See the AdsPower API docs.

Can we try it before we cancel AdsPower?

Yes, free and without a card. The Free plan runs 1 browser at once with 3 profiles. Start, Solo and Studio are each free for 7 days, so you can run your scripts on the plan you would pick.

Switching from AdsPower

Your AdsPower scripts run on Scalebrowser unchanged.

Scalebrowser answers AdsPower's local API on port 50325, so your start, stop and profile calls keep working. Around them, your agents get browsers over MCP, workflows and the Secret Layer.

Download free for Windows Read the AdsPower API docs

Free plan with 3 profiles · No credit card · Runs on your PC

One email with the download link, nothing else. Privacy

Read the AdsPower API docs

Free plan with 3 profiles · No credit card · Runs on your PC

With AdsPower

With Scalebrowser0 lines changed

open-orders.js

1import puppeteer from "puppeteer-core";
2 
3const API = "http://127.0.0.1:50325";
4const id = process.env.PROFILE_ID;
5 
6const res = await fetch(
7  `${API}/api/v1/browser/start?user_id=${id}`,
8);
9const { data } = await res.json();
10 
11const browser = await puppeteer.connect({
12  browserWSEndpoint: data.ws.puppeteer,
13});
14const [page] = await browser.pages();
15await page.goto("https://admin.shopify.com/orders");

$node open-orders.js

→ 127.0.0.1:50325AdsPower

← code 0

open-orders.js

1import puppeteer from "puppeteer-core";
2 
3const API = "http://127.0.0.1:50325";
4const id = process.env.PROFILE_ID;
5 
6const res = await fetch(
7  `${API}/api/v1/browser/start?user_id=${id}`,
8);
9const { data } = await res.json();
10 
11const browser = await puppeteer.connect({
12  browserWSEndpoint: data.ws.puppeteer,
13});
14const [page] = await browser.pages();
15await page.goto("https://admin.shopify.com/orders");

$node open-orders.js

→ 127.0.0.1:50325Scalebrowser

← code 0 data.ws.puppeteer

Orders · Nordlicht Home

admin.shopify.com/orders🇩🇪Shop EU 01

Orders

#1048Lena FischerPaid€84.00

#1047Jonas WeberPaid€129.50

#1046Mila HoffmannUnfulfilled€46.90

What stays, what starts fresh, what you gain.

Your scripts keep working as they are. Profiles and logins are set up new in four steps, and your agents get a browser of their own.

Stays the same

Your API calls
Start, stop and list profiles, groups and proxies on 127.0.0.1:50325, with code, msg and data in every answer.

Puppeteer and Selenium

A start hands back ws.puppeteer, ws.selenium and debug_port, so your scripts attach as before. Selenium brings its own chromedriver.

A browser per account
Each profile keeps its own fingerprint, cookies, proxy and extensions. Without headless it opens in a window you can work in.

Starts fresh

Port 50325
It stays closed until you turn the AdsPower API on, because sites can probe which local ports answer.
1Turn on the AdsPower API
Your profiles
They are recreated, not imported: a preset makes many at once, each with a new identity.
3Recreate your profiles from a preset
Your logins
They start fresh in each new profile: sign in once per site, or let your agent store the login in the vault without seeing it.
4Sign in once per site

What you gain

Agents over MCP
Claude Code, Cursor or ChatGPT open pages, click, type, fill forms and solve captchas in your profiles.
Workflows
Build repeat jobs from 89 blocks, run them over many profiles and start them on a schedule, by webhook or from your agent.
The Secret Layer
Your agent logs in from the vault without ever seeing the password, and it is typed only on its own site over https.
An identity from your PC
Graphics card and screen come from your real PC, and time zone and language follow each profile's proxy.
Pay by browsers at once
Plans count the browsers running at the same time: Solo runs 5 at once with 100 profiles for $49 a month.

The move, in four steps.

From the first config line to the last login, without touching a script.

Step 1: Turn on the AdsPower API
Add one line to Scalebrowser's config, or set the same address as a variable. It listens on this PC only.
Step 2: Run your scripts as they are
Close AdsPower first, since only one program can hold the port. Then start any script you already have.
Step 3: Recreate your profiles from a preset
Pick a proxy group and how many, and each new profile gets its own identity in its proxy's country.
Step 4: Sign in once per site
Each new profile starts signed out. Sign in once and it stays signed in, or let your agent store the login in the profile's vault without seeing the password.

Before you switch, short answers.

A line or two each. Every call and field is in the AdsPower API docs.

No, you create them new.

There is no import of AdsPower profiles or their logins. A preset creates many at once, each with its own identity, and in each you sign in once per site or let your agent store the login in the vault.

Your scripts are ready. Your agents are next.

Turn on the AdsPower API, run a script you already have, then connect Claude Code, Cursor or ChatGPT.

Download free for Windows