Fetch a web page and return its content and metadata via pay-per-request MPP.
What it does
Browserbase's /fetch endpoint lets AI agents retrieve the content and metadata of any web page using a headless browser, paid per request at $0.01 via the MPP (Micropayment Protocol) on Tempo. No API keys or accounts are required — callers simply include payment in the request and receive structured page data in return.
The endpoint is part of a broader Browserbase payment gateway that also offers browser session creation ($0.12/hour), web search ($0.01/request), and session management. The /fetch endpoint specifically targets the common agent need of reading a URL's rendered HTML content and associated metadata (title, description, etc.) without managing a full browser session.
During probing, the endpoint returned 404 on HEAD and GET requests rather than the expected 402 MPP challenge. The landing page at mpp.browserbase.com does list the endpoint as available via POST, so the probe may have used the wrong HTTP method (the endpoint likely requires POST). No OpenAPI schema, detailed docs, or example responses were found, so the request/response format is inferred from the endpoint's stated purpose. Treat this listing as partially verified.
Capabilities
Use cases
- —AI agents fetching rendered web page content for RAG or summarization
- —Extracting page metadata (title, description, open graph tags) from arbitrary URLs
- —Retrieving JavaScript-rendered content that simple HTTP fetches would miss
- —On-demand web page reading without managing browser infrastructure
Fit
Best for
- —AI agents that need rendered page content without running their own browser
- —One-off page fetches where a full browser session is overkill
- —Workflows requiring both page content and metadata in a single call
Not for
- —High-volume bulk crawling (per-request pricing adds up quickly)
- —Long-running interactive browser sessions (use /browser/session/create instead)
- —Free or unauthenticated access — every call requires micropayment
Quick start
npx mppx POST https://mpp.browserbase.com/fetch -d '{"url": "https://example.com"}'Example
Request
{
"url": "https://example.com"
}Endpoint
Quality
The endpoint is listed on the provider's landing page with a price ($0.01/request) and a brief description, but the probe did not capture a 402 MPP challenge (returned 404 on HEAD/GET — likely needs POST). No OpenAPI schema, no docs, no example responses are available. Request and response formats are inferred, not confirmed.
Warnings
- —Probe returned 404 on HEAD and GET; the endpoint likely requires POST but this was not verified with a POST probe.
- —No OpenAPI schema or documentation pages were found (/docs, /api, /pricing all return 404).
- —Response format is entirely unknown — example_response_json is null because no schema or sample was available.
- —Request body format (e.g., whether the field is 'url' or something else) is inferred, not documented.
Citations
- —The /fetch endpoint costs $0.01 per requesthttps://mpp.browserbase.com
- —The endpoint fetches a page and returns content + metadatahttps://mpp.browserbase.com
- —MPP settlement is on Tempo mainnet via WWW-Authenticate + mppxhttps://mpp.browserbase.com
- —No API keys or accounts required — pay-per-use with cryptohttps://mpp.browserbase.com