Overview
Lexmount Browser is a cloud browser API for AI agents that automates real web tasks. It provides isolated browser sessions on demand for browsing, clicking, and filling forms, while a Web Fetch API extracts titles, text, and links from public pages in one request. The service is designed so users do not need to deploy or maintain browsers. When creating a Cloud Browser session, users can choose Chromium or Moli based on compatibility, visual fidelity, and resource needs. Moli is described as a lighter runtime that keeps page structure and interaction state in memory and renders only when a visual view or screenshot is needed. Agents and applications can connect through Skills, MCP, SDK, or API. Pricing combines Cloud Browser, Web Fetch, and extensions per project, with Free, Pro, Pro+, and Enterprise plans.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Teams use Cloud Browser to let agents search, click, and fill forms to gather information.
- Teams use Web Fetch to extract titles, text, and links from public pages in one request.
- Teams use Cloud Browser sessions to run webpage checks with replay evidence.
- Teams use live views, replays, and extraction results to diagnose issues and review task execution.
- Teams use Moli runtime for structure-first tasks that do not require persistent Contexts, extensions, stored downloads, recording / Replay, or high-fidelity visuals.
- Teams use Chromium when unsure which runtime fits.
Features
AI assistant
Natural language interface
Workflow automation
Reviews
No reviews yet. Be the first to share your experience!
FAQ
Can I move browsers to the cloud to reduce local resource usage?
Yes. With Lexmount, page loading and page scripts run in cloud browsers. This reduces CPU and memory workload on your computer and saves deploying your own browser server. Your agent or application controls the browser through a remote connection. Start by moving one complete task, check interactions and results, then increase tasks. The controlling program must also run in an environment that stays online if tasks continue after turning off your computer.
How much of my existing Playwright script needs to change?
Start with browser creation, connection, and cleanup, then validate existing page interactions. For Chromium, connect using Playwright’s CDP connection. Create a Lexmount Chromium session and obtain its connection URL. Connect using chromium.connectOverCDP(session.connectUrl), then run existing interactions. Verify the complete workflow and explicitly close the cloud session after success, failure, or cancellation. Migrate one task before scaling up. CDP differs from a native Playwright connection, so check special APIs, extensions, and file operations separately. Files downloaded in the cloud need to be retrieved through the download API.