Cloud Browser, Web Fetch and Web Search API Pricing
USD Browser plans, Web Fetch packs, delivery terms, and practical billing examples for lexmount.com.
Pricing on lexmount.com applies per project and is shown in US dollars. The public catalog is available for product and merchant review. PayPal checkout remains disabled until merchant approval, so no payment is collected from this page today.
Browser plans
| Plan | Price | Browser hours | Concurrent browsers | Included Web Fetch | Included CAPTCHA uses |
|---|---|---|---|---|---|
| Free | US$0 | 1 | 3 | 1,000 requests | 0 |
| Pro | US$12 | 100 | 25 | 1,000 requests | 100 |
| Pro+ | US$60 | 500 | 100 | 10,000 requests | 500 |
| Enterprise | US$180 | 1,500 | 250 | 10,000 requests | 1,500 |
Paid plans are one-time purchases that provide access for one calendar month. They do not renew automatically. Each tier is priced at US$0.12 per included Browser hour. Different projects may use different plans.
Automatic CAPTCHA allowance
CAPTCHA processing is included in paid Browser plans: Pro includes 100 uses, Pro+ 500, and Enterprise 1,500 per project per usage period. Free does not include automatic CAPTCHA processing. The allowance resets with the project's plan usage period; unused uses do not carry over.
Automatic processing is disabled by default. Select “Enable automatic CAPTCHA solving” when creating a Chromium session, or pass Node.js enableCaptcha: true or Python enable_captcha=True. The option applies only to that session. See session lifecycle for the setup.
One use is deducted when a CAPTCHA task is successfully filled into the page. Detection, failed tasks, and tasks that are not filled do not deduct a use. Successful fill-in does not guarantee the target website's final acceptance; a page may present additional challenges.
An in-progress task temporarily reserves one use until its result is settled. A timeout or unknown result can therefore leave a use reserved while processing is still pending.
Separate CAPTCHA packs are not currently available, and no automatic overage charge is applied. After the allowance is exhausted, upgrade the plan or wait for the next usage period. The project's current eligibility and available allowance are checked before processing.
Web Fetch request packs
Paid projects can purchase Web Fetch requests separately. The Pro rate is US$0.47 per 1,000 requests, with the lower Pro+ and Enterprise rates shown below:
| Current plan | Rate per 1,000 | 10,000 requests | 100,000 requests | 1,000,000 requests |
|---|---|---|---|---|
| Pro | US$0.47 | US$4.70 | US$47 | US$470 |
| Pro+ | US$0.43 | US$4.30 | US$43 | US$430 |
| Enterprise | US$0.39 | US$3.90 | US$39 | US$390 |
Each request uses the current plan period's included allowance first and purchased balance second. Purchased balance does not reset with the monthly plan. Existing balance remains usable after a project moves to Free, but a Free project cannot buy another pack.
Web Search API
Web Search API is priced at US$0.75 per 1,000 requests. Every COM account includes 1,000 free Web Search requests each month, on Free, Pro, Pro+ and Enterprise. Projects linked to the same account identity share this allowance; changing a project, key or Browser plan does not grant another allowance. Web Search and Web Fetch allowances are separate.
The monthly window follows the account allowance anchor, using the existing Asia/Shanghai calendar-month calculation; it is not a rolling 30-day window. Unused requests do not carry over. A successful search counts as one request regardless of the result limit, including partial or empty successful results. Failed searches release their reservation. An unknown settlement retains its reservation until the result is reconciled or the monthly window ends, so a client timeout alone does not prove that no allowance was used.
Additional Web Search requests are not available for purchase yet, including through Stripe. The displayed rate is informational; no automatic overage charge applies. Once the included allowance is exhausted, wait for the next monthly window.
Billing examples
Example 1: Run one Pro project for a month
A project buys Pro for US$12. During that calendar month it can use 100 Browser hours, 25 concurrent browsers, and 1,000 included Web Fetch requests. If it uses only 80 Browser hours, there is no extra charge; the remaining 20 hours expire at the end of the access term.
Example 2: Add 100,000 Web Fetch requests on Pro
After the project's 1,000 included requests are exhausted, it buys a 100,000-request pack for US$47. Requests consume the included allowance before using the purchased balance. Unused purchased balance remains available after the plan period ends.
Example 3: Buy the same pack after moving tiers
The same 100,000-request pack is listed at US$47 on Pro, US$43 on Pro+, and US$39 on Enterprise. When online checkout becomes available, a quote created before a tier change will expire. Reopen checkout and confirm the new amount before paying.
Delivery, refunds, and support
- Paid access is normally provisioned to the selected project within 15 minutes after confirmed payment.
- A full refund may be requested within 7 calendar days only while all paid credits attributable to that purchase remain wholly unused.
- Purchases are one-time and do not auto-renew.
- Review the complete Refund Policy, Terms of Service, and Privacy Policy.
- Contact support@lexmount.cn or use the Contact page for payment, delivery, refund, cancellation, or dispute questions.
Where to review the catalog
- Compare plans and Web Fetch packs on the Pricing page.
- Download the current Enterprise pricing sheet (PDF) for the standard Enterprise package and custom-quote scope.
- The Pricing page currently links paid tiers to sales support while PayPal merchant approval is pending.
- After online checkout is enabled, signed-in customers will select a project and confirm the final product, amount, currency, and validity before payment.
Prices may change. The product information shown immediately before an enabled checkout will be the source of truth for that transaction.
What counts as Web Fetch usage?
Successful Extract and Dump DOM calls each report usage; capturing and then extracting a snapshot are two successful calls. Reporting can be delayed, and a client timeout does not prove that no usage was recorded. See the Web Fetch overview for integration details.
Free included Web Fetch allowance is shared across projects linked to the same account identity; replacing a key or deleting and recreating a project does not grant a fresh allowance. Purchased pack balance remains attached to the project it was bought for.