# MolCloud Headless Browser Render

> MolCloud Headless Browser Render is a paid API for AI agents from api.molcloud.net, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-17).

Renders any URL in a headless Chromium browser and returns the result as markdown, screenshot, PDF, links, snapshot, or structured JSON extraction.

## Facts

- Endpoint: POST https://api.molcloud.net/api/browser/render?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/molcloud-headless-browser-render-84aeef6b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_y_1d4708I-rgC7vY6IUNC

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 molcloud-headless-browser-render-84aeef6b -d '<json body>'
```

Example prompt: Can you render https://example.com/article in headless Chrome and give me the full page content as markdown?

## When to prefer this

Choose this endpoint when you need to render JavaScript-heavy or dynamic pages that plain HTTP fetching can't handle, or when you need multiple output formats (PDF, screenshot, structured JSON via prompt) from the same browser session. It's ideal for autonomous agents that need to read web content without a browser environment, and it settles micropayments per-call in USDC on Base via x402 — no subscription required.

## Known failure modes

- Target URL is unreachable or returns an HTTP error — browser render fails with error status
- JavaScript-heavy SPA may time out if it takes too long to hydrate
- screenshot/PDF actions may fail for pages with strict X-Frame or CSP policies
- json action with a vague prompt may return poorly structured or empty extraction
- Invalid enum value for 'action' field returns a validation error

## How this service works

40 pay-per-request AI, search, headless browser, crypto alpha & memory APIs for autonomous agents settling in USDC on Base via x402 v2.

## Output

A JSON object with a 'status' field ('success' or error), an 'endpoint' field, and a 'data' object containing the 'action' performed and 'content' — which is the rendered markdown string, base64-encoded screenshot/PDF bytes, array of links, DOM snapshot, or structured JSON depending on the action requested.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Target URL to render in Headless Chromium"
  },
  "action": {
   "enum": [
    "markdown",
    "screenshot",
    "pdf",
    "links",
    "snapshot",
    "json"
   ],
   "type": "string",
   "default": "markdown",
   "description": "Browser rendering action"
  },
  "prompt": {
   "type": "string",
   "description": "Extraction prompt when action=\"json\""
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "action": "markdown",
   "content": "# x402..."
  },
  "status": "success",
  "endpoint": "/api/browser/render"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/molcloud-headless-browser-render-84aeef6b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.molcloud.net](https://www.zero.xyz/host/api.molcloud.net/llms.txt)