# HALOWERK laufwerk – Browser Visible Proof

> HALOWERK laufwerk – Browser Visible Proof is a paid API for AI agents from lauf.halowerk.com, paid per call via x402, $0.016/call, status unknown (last checked 2026-11-18).

Loads a web page in a real browser and captures a visual proof (screenshot or rendered element) of a specific CSS selector, returning verifiable evidence of what is visibly rendered at that URL.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/browser/visible-proof?utm_source=zero.xyz
- Price: $0.016/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-laufwerk-browser-visible-proof-16d075ca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O9Ipc3xiWZI0co0jo1kac

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 halowerk-laufwerk-browser-visible-proof-16d075ca -d '<json body>'
```

Example prompt: Can you grab a visual proof of the main hero banner on https://example.com by targeting the CSS selector '.hero-banner' — I need to verify what's actually being shown there?

## When to prefer this

Choose this endpoint when you need verifiable, browser-rendered visual evidence of a specific element on a live webpage — especially for ad verification, compliance auditing, UI checks, or any use case where you must prove what a real browser actually displays at a CSS selector. Prefer this over simple HTTP scraping when JavaScript rendering matters or when a visual artifact is required as proof.

## Known failure modes

- URL does not match required HTTPS pattern — returns validation error
- CSS selector not found in the rendered page — element may not exist or may be dynamically loaded after timeout
- Page load timeout or network error preventing browser from rendering the URL
- Selector string exceeds 200 character limit — returns schema validation error
- URL exceeds 2048 character limit — rejected at input validation
- Payment not completed via x402 protocol — 402 response with payment requirements

## How this service works

HALOWERK laufwerk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

A JSON response containing visual proof data for the specified CSS selector on the given URL — typically including screenshot image data or rendered element evidence showing what is visibly displayed in a real browser at that location.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "pattern": "^https://[^@\\s]+$",
   "maxLength": 2048,
   "minLength": 10
  },
  "selector": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-browser-visible-proof-16d075ca/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lauf.halowerk.com](https://www.zero.xyz/host/lauf.halowerk.com/llms.txt)
