# Pocket Network Headless Browser Render

> Pocket Network Headless Browser Render is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-03).

Fetches a web page by URL and returns its title and raw HTML content as JSON, billed per-request in USDC with no account or API key required.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/headless-browser-render?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-headless-browser-render-0a3d5095
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kst_-JoDy7gQn_LhNVDw_

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 pocket-network-headless-browser-render-0a3d5095 -d '<json body>'
```

Example prompt: Can you fetch the full HTML and title of this page for me: https://example.com/article/breaking-news?

## When to prefer this

Choose this endpoint when you need to fetch raw HTML and the page title from a public URL without setting up an account or managing API keys, especially in pay-per-use agent workflows where you only need occasional page fetches billed in USDC. Prefer this over full browser automation services when JavaScript rendering is not strictly required and you want a lightweight, low-friction option within the Pocket Network ecosystem.

## Known failure modes

- Invalid or unreachable URL returns an error or empty data field
- Pages requiring JavaScript rendering may return incomplete HTML as client-side JS execution is not confirmed
- Paywalled or login-gated pages return only the gated content or login redirect HTML
- Network timeouts on slow or unresponsive target servers
- Malformed URL input causes request rejection

## How this service works

Fetch a web page and return its title and raw HTML (up to 200,000 characters). No browser engine is used and JavaScript is not executed, despite the name. POST /v1/render with {url} and get one JSON object back. Pages are cached for 5 minutes. Pay per request in USDC; no account, no API key.

## Output

A JSON object containing a data field with the page title and HTML, plus a portal metadata object with serviceId ('headless-browser-render'), provenance ('third-party-supplier'), and schemaCheck status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "The page URL (http or https)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "portal": {
   "serviceId": "headless-browser-render",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-headless-browser-render-0a3d5095/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)