# Hyperbrowser Web Page Fetch

> Hyperbrowser Web Page Fetch is a paid API for AI agents from api.hyperbrowser.ai, paid per call via x402, $0.001/call, status healthy (last checked 2026-09-13, last successful call 2026-08-31).

Fetches the full content of a web page by URL, returning structured or raw output suitable for AI agent processing

## Facts

- Endpoint: POST https://api.hyperbrowser.ai/x402/web/fetch
- Price: $0.001/call
- Payment: x402
- Status: healthy
- Last checked: 2026-09-13
- Last successful call: 2026-08-31
- Success rate: 100% of calls made through Zero
- Rating: 5.0 / 5 from 1 review
- Activations on Zero: 1
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hyperbrowser-web-page-fetch-a3ecc968
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ObQxXKA6LV3IsF-3jJiAA

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 hyperbrowser-web-page-fetch-a3ecc968 -d '<json body>'
```

Example prompt: Can you fetch the content of https://example.com/pricing and pull out the text so I can see what's on that page?

## When to prefer this

Choose this endpoint when you need to retrieve the live content of a specific, known URL for a single page fetch — especially when you want AI-friendly structured output from a headless browser that handles JavaScript rendering. Prefer this over generic HTTP GET approaches when the target page is dynamic or JS-rendered. Use the sibling web search endpoint instead when you don't have a specific URL and need to discover pages by query.

## Known failure modes

- URL is unreachable or returns a non-200 HTTP status — endpoint may return an error or empty content
- Page requires JavaScript-heavy rendering that times out
- Anti-bot protections (CAPTCHAs, rate limiting) block the fetch
- Malformed or missing URL in request body causes a 400-level error
- Payment not processed — x402 payment required error if USDC not provided

## How this service works

Fetch a web page (JSON body includes url, outputs, etc.)

## Output

Returns the fetched web page content, which may include raw HTML, extracted plain text, or structured data depending on the output options specified in the request body. The response reflects the live state of the page at the time of the request.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hyperbrowser-web-page-fetch-a3ecc968/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.hyperbrowser.ai](https://www.zero.xyz/host/api.hyperbrowser.ai/llms.txt)