# Browserbase Page Fetch

> Browserbase Page Fetch is a paid API for AI agents from x402.browserbase.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Fetches a web page via headless browser and returns its content, headers, and metadata.

## Facts

- Endpoint: POST https://x402.browserbase.com/fetch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/browserbase-page-fetch-cc30dbcf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9QUOXKN-2qLRsywDrA_Qu

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability browserbase-page-fetch-cc30dbcf -d '<json body>'
```

Example prompt: Can you fetch the full page content of https://example.com/pricing using a real browser so I get the rendered HTML, status code, and content type?

## When to prefer this

Choose this endpoint when you need a real headless browser to fetch and render a web page — especially for JavaScript-heavy sites where a plain HTTP GET would return incomplete content. It is ideal for single-page fetches where you need rendered HTML, status codes, and content type metadata. Prefer it over simple HTTP clients when the target page requires JavaScript execution or browser-like behavior.

## Known failure modes

- Invalid or unreachable URL returns non-200 status code in the statusCode field
- Page with heavy bot protection may return empty or blocked content
- Timeout on slow-loading pages may result in partial or empty content
- Malformed request body may result in a 400 error
- Payment failure or insufficient funds returns a 402 error

## How this service works

Fetch a page and return content, headers, and metadata. $0.01 per request.

## Output

Returns a JSON object containing a session ID, the full page content as a string (rendered HTML), the HTTP status code, and the content type of the response.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string"
  },
  "content": {
   "type": "string"
  },
  "statusCode": {
   "type": "number"
  },
  "contentType": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/browserbase-page-fetch-cc30dbcf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.browserbase.com](https://www.zero.xyz/host/x402.browserbase.com/llms.txt)