Extend a running Browserbase headless browser session by adding more time via MPP payment.
What it does
The Browserbase `POST /browser/session/:id/extend` endpoint lets callers add more time to an already-running headless browser session. It is part of the Browserbase pay-per-use browser infrastructure, which provides headless browser sessions, web search, and page fetching for AI agents — all purchasable without API keys or accounts, using crypto micropayments via the MPP (and x402) protocols.
Browserbase browser sessions are priced at $0.12/hour. The extend endpoint presumably charges proportionally for the additional time requested. Payment settles on the Tempo mainnet chain via the MPP protocol (WWW-Authenticate challenge with mppx tooling). The service also supports x402 via USDC on Base. Other endpoints in the suite include session creation, status checks, session termination, web search ($0.01/request), and page fetching ($0.01/request).
Note: During probing, this endpoint returned 404 on both HEAD and GET requests rather than the expected 402 MPP challenge. This is likely because the endpoint requires a POST method and a valid session ID in the URL path (`:id` is a path parameter). Without a real session ID, the server returns 404. The endpoint is expected to be live when called correctly against an active session, but this could not be confirmed directly.
Capabilities
Use cases
- —Extending a long-running browser automation session that needs more time than originally estimated
- —Keeping a headless browser session alive for multi-step web scraping or interaction workflows
- —Dynamically adding compute time to an agent's browser session without restarting
Fit
Best for
- —AI agents that need headless browser sessions with flexible duration
- —Workflows where session length is unpredictable and needs on-the-fly extension
- —Developers who want pay-per-use browser infrastructure without managing API keys or accounts
Not for
- —Creating new browser sessions (use /browser/session/create instead)
- —Use cases requiring free or flat-rate browser access without per-hour billing
- —Scenarios where the session ID is not already known from a prior create call
Quick start
npx mppx POST https://mpp.browserbase.com/browser/session/SESSION_ID/extendEndpoint
Quality
The endpoint did not return a 402 MPP challenge during probing (returned 404), likely due to the path parameter requiring a valid session ID and POST method. No OpenAPI schema, no detailed docs, and no request/response examples are available. Pricing and basic purpose are inferred from the landing page, but specifics about the extend endpoint's request body and response are unknown.
Warnings
- —Endpoint returned 404 on HEAD and GET probes — likely requires POST with a valid session ID; could not confirm live 402 challenge
- —No documentation pages found (/docs, /api, /pricing, /README all return 'Cannot GET')
- —No request or response schema available for this endpoint
- —Exact pricing for extend calls is not documented — $0.12/hour is the session rate but per-extend cost is unconfirmed
Citations
- —Browser sessions are priced at $0.12/hourhttps://mpp.browserbase.com
- —POST /browser/session/:id/extend adds more time to a sessionhttps://mpp.browserbase.com
- —MPP settlement uses Stripe Tempo chain (mainnet)https://mpp.browserbase.com
- —Service supports x402 via USDC on Basehttps://mpp.browserbase.com
- —No API keys or accounts required — pay-per-use with cryptohttps://mpp.browserbase.com