Local-only service
The service listens on 127.0.0.1 and is designed for tools running on the same computer.
Run a local-only service, manage profile lifecycles with JSON requests, and receive CDP endpoints for established browser automation frameworks.
POST /browser/open{ "profileId": "demo-01" }_
The service listens on 127.0.0.1 and is designed for tools running on the same computer.
Endpoints use POST with JSON bodies and return a consistent success or failure envelope.
Opening a profile returns HTTP and WebSocket CDP endpoints for automation clients.
From setup to execution, every capability maps to real work and keeps the context clear and inspectable.
04capabilitiesKeep context visible from initial setup through daily operations.
Open the API & MCP page and start the service on its displayed loopback address.
Use /browser/list or /browser/create and retain the returned profile identifier.
Call /browser/open, then connect the returned CDP endpoint to your automation client.
Connect established browser-control frameworks to Ovobrowser profile lifecycles.
Launch repeatable, configured environments from local test runners.
Add profile management to schedulers, dashboards, and controlled local workflows.
No. The current service listens on 127.0.0.1 and is intended for local applications on the same computer.
The current loopback-only service does not require a token or additional authentication header. Do not expose it through an external tunnel or public proxy.
The returned CDP endpoints can be used with compatible clients such as Playwright, Puppeteer, and Selenium.
The current endpoints use POST requests with JSON bodies. Responses use a consistent success/data or success/message envelope.
Download Ovobrowser free and organize accounts, proxies, fingerprints, and team collaboration in one clear workspace.
OvobrowserWindows · macOS