# HALOWERK laufwerk – Browser Text-Contains Proof

> HALOWERK laufwerk – Browser Text-Contains 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-16).

Loads a public HTTPS page in a headless browser, queries a CSS selector, and verifies that the matched element contains a specified text fragment, returning a proof of presence or absence.

## Facts

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

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-contains-proof-474da9b8 -d '<json body>'
```

Example prompt: Can you check whether the element matching '.price-tag' on https://example-shop.com/product/42 actually contains the text '$19.99'?

## When to prefer this

Use this endpoint when you need a cryptographically-accountable, real-browser proof that a specific piece of text is present (or absent) in a CSS-selected element on a live public HTTPS page — especially in automated workflows, compliance checks, or agent pipelines that require verifiable evidence rather than a simple HTTP scrape. Prefer it over raw HTTP fetching when JavaScript rendering is required for the content to appear, or when you need the check to be auditable via x402 payment provenance.

## Known failure modes

- URL is not HTTPS or is malformed — request rejected
- CSS selector matches no element on the page — returns no-match or error
- Page requires authentication or hits a login wall — refused
- Page triggers CAPTCHA — refused
- Network timeout or page load failure — error response
- Expected fragment not found — returns false/non-match proof
- Selector string too long or URL too long — validation error

## How this service works

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

## Output

A JSON object indicating whether the specified CSS selector on the given HTTPS page contains the expected text fragment, typically including a boolean match result and details about what was actually found in the matched element.

## 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_fragment": {
   "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-contains-proof-474da9b8/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)
