Browserbase on x402: buy browser time for an agent

On this page

We followed Browserbase's x402 listing through to its session documentation to understand what a business is actually buying. We've pulled out the starting endpoint, time-based price and connection details so you can assess a browser task without piecing the access model together yourself.

Our main finding is straightforward: the purchase supplies browser time and a connection. Your agent or automation still has to operate the browser and return the result. That distinction matters when a facilities consultant needs to use a supplier's product selector to find specifications.

The homepage listing leads to Browserbase's entry on Agentic Market. The provider's integration documentation confirms its direct service at x402.browserbase.com. Below, we work through a proposed lookup and the documented cost of the session it would use.

A practical browser task

Consider an illustrative comparison of replacement air filters. The consultant already knows the supplier's website, but its catalogue reveals dimensions and compatible equipment only after choosing a range and model.

A bounded browser task would be: navigate the public selector, inspect the requested model and return the displayed dimensions with the source URL. The agent would not log into a customer account, submit an enquiry or place an order as part of this task.

That scope makes it possible to recognise completion. “Browser session created” is only the start. The consultant needs the correct product details and enough source context to distinguish neighbouring models.

Create the session

The documented entry point is POST https://x402.browserbase.com/browser/session/create. Its JSON body specifies the prepaid time requested. This sample is illustrative; no paid session was created for this article:

{
  "estimatedMinutes": 15
}

Browserbase's x402 quickstart documents a paid response containing sessionId, connectUrl, paidMinutes and expiresAt, with pricing information. connectUrl is the WebSocket connection the browser client uses. The quickstart demonstrates connecting through Playwright or Puppeteer.

The request body does not contain the supplier URL or instructions for the product selector. Those belong in the browser work performed after connecting. This distinction matters when estimating what you have bought: the session endpoint is not a finished product-research service.

For the illustrative task, the automation would then open the known supplier page, make the permitted selections and record the displayed fields. If the page exposes several versions, it should keep the version labels with the dimensions rather than combine them into one answer.

What browser time costs

As checked on 7 September 2026, Browserbase's published x402 prices are 0.12 USDC per hour, including 0.03 USDC for 15 minutes. The provider's live payment-gateway page displays the same hourly rate. The integration documentation describes USDC payments on Base without a Browserbase account or API key.

These prices describe browser time. They do not establish the full cost of an agent that reasons about the page, retries an interaction or reviews the extracted details. Include those separately when comparing ways to complete the job.

The quickstart also documents GET /browser/session/:id/status to inspect time remaining and POST /browser/session/:id/extend to buy more time. Use the identifier returned for your own session.

The public Agentic Market API search returned session-specific extension URLs when we checked it. Those are not reusable starting points for a new session. Follow Browserbase's create endpoint above and its current documentation.

Choose a browser when the interaction matters

Before buying browser time, identify the interaction the task requires. If you only need to find source URLs, Exa search or Tavily search may cover that contribution. If you have a URL and need its readable text, investigate content retrieval before specifying a full browser workflow.

Browserbase's own browser-agent guidance distinguishes search and fetch from browser sessions, presenting the simpler tools as faster and cheaper for their respective jobs. A browser earns its place in the example because the product selector must be operated.

A first trial should use a task whose output you can verify directly. Give the agent the supplier page, exact model and fields required. Inspect its returned dimensions against the page before using them in a client recommendation. Record whether the browser work completed within the purchased time and whether the evidence was sufficient.

To proceed, open Browserbase's linked quickstart for the payment client and connection code. Our x402 explanation covers the purchase mechanism, while how agents buy services connects the session to the wider job. This article is based on documentation and listing checks; we have not tested paid session creation or the illustrative product-selector task.