Lexmount DocsDocumentation Overview
Read Lexmount docs by console quick start, SDK integration, demos, and integrations.
Lexmount docs follow the same path as the product quick start: verify one cloud browser flow in the console first, then move the same flow into SDK and agent code.
Start here
If this is your first integration, open Quick Start first. It walks through API Key -> Session -> View navigation -> Python SDK with product screenshots.
Reading Path
1. Understand the console flow
The console quick start maps to four actions:
| Step | What you do in the console | What it becomes in code |
|---|---|---|
| API Key | Create credentials and confirm Project ID | Initialize the SDK client |
| Session | Launch one cloud browser instance | client.sessions.create() |
| View navigation | Open the remote screen and verify navigation | Connect to the browser through CDP |
| SDK integration | Move the same flow into code | Playwright / agent execution |
The goal is not to show every feature. The goal is to confirm that credentials, browser instance creation, remote view, and code connection all work.
2. Choose an SDK
- Python SDK Quick Start: Closest to the current
/quick-startpage and recommended for the first agent browser task. - Node.js SDK Quick Start: For TypeScript / Node.js service integrations.
SDK docs explain the relationship between sessions, View, connect URL, CDP connection, and cleanup.
3. Then read the examples
The examples are not a separate onboarding flow. They are scenario slices of the same quickstart path:
demo.py: Minimal loop: create session, connect browser, visit a page.inspect_url_demo.py: Keep View open for manual observation and debugging.session_downloads.py: Retrieve files downloaded by the remote browser.context_basic.py,extension_basic.py,proxy_demo.py: Read after the basic path works.
See Python Examples for detailed explanations.
Other Integration Entrances
- WebFetch: A web extraction API for content retrieval scenarios.
Core Concepts
Session
A session is one cloud browser instance. After creation it returns a session ID, remote View entry, and CDP connection address. Close the session after the task to release cloud resources.
View
View is the remote browser screen. Use it to observe, verify navigation, and take over when needed. It is the same cloud session that SDK code controls.
Connect URL
connect_url is the CDP endpoint used by Playwright / Puppeteer. Once the console flow is verified, the SDK uses this address to hand the browser to code.