# HALOWERK laufwerk Browser Text Exact Proof

> HALOWERK laufwerk Browser Text Exact 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).

Visits a URL in a headless browser, finds an element by CSS selector, and verifies that it contains a specific expected text string, returning a proof of the match.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/browser/text-exact-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-text-exact-proof-acaa05d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vd5jBt17qjgNuN_iZL_VR

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-text-exact-proof-acaa05d4 -d '<json body>'
```

Example prompt: Check if the element with CSS selector '#status-banner' on https://example.com/dashboard contains exactly the text 'All systems operational' and give me proof of the result.

## When to prefer this

Use this endpoint when you need a verifiable, browser-rendered proof that a specific DOM element on a live HTTPS webpage contains an exact text string. It is especially useful for post-deployment checks, content compliance auditing, monitoring UI copy, or generating tamper-evident proof of what a webpage displays at a given selector. Prefer it over simple HTTP scraping when JavaScript rendering is needed to hydrate the DOM, or when you specifically need an exact-match assertion rather than fuzzy text extraction.

## Known failure modes

- URL unreachable or returns non-200 status — verification fails with error
- CSS selector not found in the DOM — returns no-match or selector error
- Text content exists but does not exactly match expected_text — returns failed proof
- URL pattern validation fails if URL does not begin with https:// — rejected at input
- Timeout loading the page in the headless browser — returns timeout error
- Expected text or selector exceeds maximum length constraints — rejected at input

## How this service works

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

## Output

A JSON response containing the verification outcome: whether the specified CSS selector on the given URL contains exactly the expected text, along with a proof artifact (match status, actual text found, selector matched, and URL visited).

## 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
  },
  "expected_text": {
   "type": "string",
   "maxLength": 2000,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-browser-text-exact-proof-acaa05d4/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)
