Skip to main content
The Browser Use integration on the Vercel Marketplace gives a Vercel project a Browser Use account, billing through Vercel, and a BROWSER_USE_API_KEY environment variable. From there you run hosted browser agents or connect your own code to a cloud browser.

Install from the Marketplace

1. Install the integration In the Vercel dashboard open Integrations → Browse Marketplace, choose Browser Use, and select Install. Pick a plan (start with Free) and connect the resource to the project that will call Browser Use. 2. Check the environment variable Vercel adds BROWSER_USE_API_KEY to the connected project for production, preview, and development. Pull it into your local environment:
3. Open Browser Use Select Open in Browser Use on the resource page. Vercel signs you in to cloud.browser-use.com without a separate account, where you can watch runs, replay sessions, and manage the project.

Next.js

1. Install the SDK
2. Add a route handler The client reads BROWSER_USE_API_KEY from the environment. Keep it server-side: call Browser Use from a route handler or server action, never from the browser.
app/api/research/route.ts
3. Call it
Runs can outlast a single Vercel function invocation. For anything longer than your function’s maxDuration, return run.id right away and read progress from a second route with client.runs.status(runId) and client.runs.events(runId). See Observability for the event stream and Structured output for returning JSON your app can validate.

Vercel eve agents

Give an eve agent a cloud browser with the official package. It adds the open_cloud_browser and stop_cloud_browser tools plus a browsing skill, and your API key never leaves the app runtime.
With BROWSER_USE_API_KEY set, ask the agent to “open example.com and tell me the title”. To start from a working app, deploy the Browser Agent Template: a Next.js chat UI, an eve agent, and a live browser panel in one codebase.

Bring your own automation

If you already drive browsers with Puppeteer or Playwright, use the cloud browser without the hosted agent:
See the Browser Infrastructure quickstart for Playwright, Selenium, and curl.

Billing and limits

Usage is billed through your Vercel account on the plan you picked at install time. Keys in one project share concurrency and credits; read Concurrency and limits before running many tasks in parallel. Changing the plan in Vercel updates the Browser Use project automatically.