# HALOWERK laufwerk Checked-Proof

> HALOWERK laufwerk Checked-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-17).

Loads a webpage in a real headless browser, finds a checkbox or toggle by CSS selector, and verifies whether it is checked or unchecked as expected.

## Facts

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

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-checked-proof-429cd3cc -d '<json body>'
```

Example prompt: Can you verify whether the 'Subscribe to newsletter' checkbox on https://example.com/signup is currently checked? The CSS selector is '#newsletter-opt-in' and I expect it to be checked.

## When to prefer this

Use this endpoint when you need cryptographic or auditable proof that a specific checkbox or toggle on a live public HTTPS page is in a particular checked/unchecked state, especially for compliance, QA, or automated monitoring scenarios. Prefer it over general-purpose scraping endpoints when the target is specifically a checkbox element and you need a boolean assertion with evidence. It is not suitable for pages behind authentication walls or CAPTCHAs.

## Known failure modes

- URL does not match required HTTPS pattern or is too short — 400 error
- CSS selector not found on page — element not found error
- Page requires login or hits a CAPTCHA wall — endpoint refuses and returns an error
- Selector matches a non-checkbox element — may return unexpected result
- Page load timeout or unreachable URL — connection error
- expected_checked value not provided — may default or return validation error

## How this service works

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

## Output

A JSON object containing the proof of the checkbox's actual checked state on the live page, whether it matched the expected value, the selector used, and contextual metadata from the headless browser session.

## 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_checked": {
   "type": "boolean"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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