ข้ามไปยังเนื้อหา

ยังไม่มีหน้านี้ในภาษาของคุณ คุณกำลังอ่านข้อความภาษาอังกฤษ

AI and automation

Puppeteer, Playwright and Selenium

Connect your code to an open ARMANOS profile: with its fingerprint, cookies and proxy. Every profile has its own debugging address.

About the service

Puppeteer, Playwright and Selenium drive a browser from code. All three attach to a Chromium debugging address.

What you get with ARMANOS

  • Its own debugging address per profile

    Every profile on the ARMANOS Browser engine returns a debugging address of its own.

  • Fingerprint, cookies and proxy in place

    A script works in a profile that is already open with its own settings.

  • A token on every call

    The interface listens on this computer only and opens with your token.

  • Several profiles at once

    Run one driver per profile: each sees only its own profile.

  • Signs of automation

    navigator.webdriver stays false, the same as in a profile without automation.

  • 78 API calls

    Create, start and stop profiles, read cookies, run flows and tasks.

How to connect

  1. Open For developers

    The For developers screen is in the left column, in the Automation section.

    The For developers screen in the Automation section.
  2. Turn on Enable local API

    The switch sits at the top of the card. The state next to it reads Running.

    With the switch on, the state to the right reads Running.
  3. Open a profile through the API

    A POST /api/v1/browser/start request with the profile number. The answer carries the debugging address of that profile.

    Important: The ARMANOS Browser engine gives a profile its own debugging address.

  4. Attach your code

    Puppeteer: puppeteer.connect with the ws address. Playwright: connect_over_cdp. Selenium: the debuggerAddress option.

Questions and answers

Which engine is needed?
ARMANOS Browser: only it gives every profile its own debugging address.
Which ChromeDriver should I take?
One of the same main version as the engine. A GET /api/v1/app/state request names the version.
Does the profile close with the driver?
No. driver.quit() ends the driver, and the profile stays open until you close it.

Connect your code to profiles

Create an ARMANOS account, switch on the local API and open your first profile from a script.