# HALOWERK laufwerk – Browser Attribute Proof

> HALOWERK laufwerk – Browser Attribute 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).

Fetches a live web page and verifies the value of a specified HTML attribute on a given CSS-selected element, returning proof of that attribute's current state.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/browser/attribute-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-browser-attribute-proof-1aa49d6f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bBUKxYFR4xKQwJbyWQkhx

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-attribute-proof-1aa49d6f -d '<json body>'
```

Example prompt: Can you check the live page at https://example.com/signup and confirm whether the email input field (selector: #email) has its 'required' attribute set — I want to know if that field is mandatory?

## When to prefer this

Use this endpoint when you need live, on-demand proof of a specific HTML attribute value on a real webpage — particularly for accessibility audits, form validation checks, UI regression testing, or any workflow where you need a verifiable snapshot of an element's attribute state at a given moment. Prefer this over generic scraping endpoints when you need attribute-level specificity rather than full page content.

## Known failure modes

- URL is unreachable or returns a non-200 status — endpoint returns an error indicating the page could not be fetched
- CSS selector matches no element on the page — returns a not-found or null result
- Requested attribute is not present on the matched element — returns null or absent indicator
- URL fails HTTPS pattern validation — returns a 400 schema validation error
- Attribute enum value not in allowed list — returns a 422 or schema rejection error
- Page requires authentication or JavaScript rendering that cannot be satisfied — may return incomplete or empty result

## How this service works

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

## Output

A JSON object containing the matched element's current attribute value, whether it matches the expected value (if provided), and contextual proof metadata such as the selector used, the attribute checked, and the timestamp of the live page fetch.

## 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
  },
  "attribute": {
   "enum": [
    "type",
    "role",
    "name",
    "id",
    "alt",
    "title",
    "placeholder",
    "aria-label",
    "aria-hidden",
    "aria-disabled",
    "aria-expanded",
    "aria-pressed",
    "tabindex",
    "rel",
    "target",
    "lang",
    "method",
    "required",
    "disabled",
    "readonly",
    "pattern",
    "min",
    "max",
    "step",
    "minlength",
    "maxlength"
   ]
  },
  "expected_value": {
   "type": [
    "string",
    "null"
   ],
   "maxLength": 2000
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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