Pay-per-use headless browser sessions via MPP — no API keys, no accounts, just pay and connect.
What it does
Browserbase's MPP endpoint at `/browser/session/create` provisions on-demand headless browser sessions that AI agents can control remotely. The service follows the MPP (Micropayment Protocol) wire format: an unauthenticated request receives a 402 challenge with payment options, and once payment is submitted the session is created and connection details returned. No API keys or account registration are required.
The endpoint supports two settlement methods. The **Tempo** method settles on-chain (chain ID 4217) with a charge of 10,000 base units of pathUSD (6 decimals → $0.01 per request to create, with the session itself billed at $0.12/hour according to the landing page). The **Stripe** method settles via card rails at $1 USD per call. The landing page lists additional endpoints for checking session status, extending session time, terminating sessions, performing web searches ($0.01/request), and fetching pages ($0.01/request), though this listing covers only the session-create endpoint.
The request body accepts at least an `estimatedMinutes` field to pre-allocate session duration. Detailed API documentation is not currently available — the `/docs`, `/api`, and `/pricing` paths all return 404. The endpoint is live: the probe captured valid 402 challenges on both Tempo and Stripe methods with an expiry date of April 2026.
Capabilities
Use cases
- —AI agents that need to interact with live web pages (fill forms, click buttons, navigate)
- —Automated web scraping pipelines that require a full browser environment
- —QA and testing workflows that spin up disposable browser sessions on demand
- —Research agents that browse, search, and extract structured data from the web
- —Tool-use LLM chains that need authenticated or JavaScript-rendered page access
Fit
Best for
- —AI agents needing ephemeral browser sessions without managing infrastructure
- —Developers who want pay-per-use browser access without account signup
- —Crypto-native or MPP-compatible agent wallets settling micropayments per session
Not for
- —Long-running persistent browser sessions (pricing is hourly, sessions are ephemeral)
- —Use cases requiring detailed API documentation or SLA guarantees (docs are currently missing)
Quick start
npx mppx https://mpp.browserbase.com/browser/session/create -d '{"estimatedMinutes": 30}'Example
Request
{
"estimatedMinutes": 30
}Endpoint
Quality
The endpoint is live with valid 402 challenges on two settlement methods, and the landing page provides pricing and a list of endpoints. However, there is no OpenAPI schema, no detailed docs (all doc paths return 404), and no example response body, so the integration surface must be inferred.
Warnings
- —No API documentation available — /docs, /api, /pricing, /README all return 404.
- —No response schema or example response is available; the shape of the session-create response is unknown.
- —Stripe method charges $1.00 per call while Tempo charges ~$0.01 — significant price difference between settlement methods that is not explained.
- —The estimatedMinutes request field is inferred from the landing page example only; full request schema is undocumented.
Citations
- —Browser sessions are priced at $0.12/hour, search at $0.01/request, fetch at $0.01/requesthttps://mpp.browserbase.com
- —Endpoint supports x402 and MPP protocols with Tempo and Stripe settlementhttps://mpp.browserbase.com
- —Request body accepts an estimatedMinutes fieldhttps://mpp.browserbase.com
- —Tempo settlement uses chain ID 4217 with an amount of 10000 base unitshttps://mpp.browserbase.com/browser/session/create
- —Stripe settlement charges $1 USD per call via card payment methodhttps://mpp.browserbase.com/browser/session/create
- —Description states: Pay-per-use browser sessions with crypto. No API keys, no accounts.https://mpp.browserbase.com