Collect from logged-in sites through persistent profiles.

Before you start

• Accounts on the target sites that your terms of service permit you to use this way
• AliasMode installed and the Local API available at 127.0.0.1:50400
• A Playwright or Puppeteer collector
• A residential proxy per profile matching the account's usual region

Step-by-step

1. 1

   Confirm you may collect, then how much

   Check the site's terms, robots directives, and your account agreement. Decide a sustainable rate — pages per minute and runs per day — before writing code.

2. 2

   One profile per site account

   Create an AliasMode profile per target account: scrape·site·account-name. If a site bans an account, the blast radius is one profile.

3. 3

   Match the proxy to the account

   Attach a residential proxy in the region the account normally logs in from, and preflight. A familiar IP is the cheapest anti-challenge measure there is.

4. 4

   Seed the login by hand

   Log in manually once inside the profile and solve any challenge personally. Collectors never handle the login form; they inherit the session.

5. 5

   Start the session per run

   Start the profile through the Local API at the beginning of each run.

   Step 5

   const res = await fetch('http://127.0.0.1:50400/api/v1/browser/start?user_id=' + profileId);
   const { data } = await res.json();
   const browser = await chromium.connectOverCDP(data.ws.puppeteer);

6. 6

   Collect at a human pace

   Throttle requests, randomize pacing modestly, and stop on rate-limit signals rather than pushing through. Long, slow, boring runs beat fast, hot ones.

   Step 6

   const context = browser.contexts()[0];
   for (const url of queue) {
     await page.goto(url);
     // extract, then wait — keep it slow and steady
     await page.waitForTimeout(3000 + Math.random() * 4000);
   }

7. 7

   Stop and sync

   Close the browser and stop the profile after each run so the session is saved cleanly for tomorrow.

   Step 7

   await browser.close();
   await fetch('http://127.0.0.1:50400/api/v1/browser/stop?user_id=' + profileId);

8. 8

   Monitor session health

   If a run lands on a login page or challenge, stop that profile, re-seed the login manually, and investigate the rate before resuming.

The AliasMode workflow

1. 1

   Profiles as site credentials

   One profile per site account keeps logins, cookies, and fingerprint history attributable to one identity.

2. 2

   Local API as the run switch

   Start and stop sessions from your collector's scheduler; nothing runs outside a managed session.

3. 3

   Preflight per run

   Confirm the exit IP region before each run so the account never sees a surprise geo.

Verify it worked

• Runs land on logged-in pages with no login flow executed by code.
• Collection rates match the documented throttle, sampled from run logs.
• Stopping a run mid-way leaves a stoppable, resumable state — no orphan browser.
• Account health is stable: no new challenges or warnings across a month of runs.

Cautions

• Scraping can breach a site's terms even when the data itself is public — get the legal basis right for your jurisdiction and data types.
• Never collect personal data without a lawful basis; authenticated access is not consent.
• Pushing through rate limits risks the account and, on shared IPs, the proxy's reputation.