# HALOWERK laufwerk Color Contrast Compare

> HALOWERK laufwerk Color Contrast Compare is a paid API for AI agents from lauf.halowerk.com, paid per call via x402, $0.025/call, status unknown (last checked 2026-11-17).

Compares color contrast accessibility quality scores between a baseline webpage and a candidate webpage, optionally enforcing a maximum allowed score regression.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/quality/compare-color-contrast?utm_source=zero.xyz
- Price: $0.025/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-color-contrast-compare-bf798c54
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SraAIOj8heA8K_M_vmoT6

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-color-contrast-compare-bf798c54 -d '<json body>'
```

Example prompt: Compare the color contrast quality of my redesigned page at https://staging.example.com/home against the current production page at https://www.example.com/home and flag it if the new version is more than 10% worse (allowed_score_regression: 0.1).

## When to prefer this

Use this endpoint when you need an automated, quantitative comparison of color contrast accessibility quality between two specific URLs — particularly useful in CI/CD pipelines, pre-deployment accessibility audits, or design review workflows where you want to enforce a maximum allowed regression from a known-good baseline. Prefer this over manual WCAG checkers when you need a programmatic, payable API call with a regression threshold rather than a one-off visual audit.

## Known failure modes

- Invalid or inaccessible URL returns an error (URL must match ^https://[^@\s]+$)
- Baseline or candidate page returns HTTP error or is unreachable, causing request failure
- allowed_score_regression out of range [0,1] triggers validation error
- Payment not provided or insufficient USDC balance causes x402 payment rejection
- Candidate page renders inconsistently (dynamic content), leading to variable scores across runs

## How this service works

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

## Output

A JSON response containing color contrast quality scores for both the baseline and candidate URLs, a comparison delta, and a pass/fail decision based on the allowed_score_regression threshold (if provided).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "baseline_url": {
   "type": "string",
   "pattern": "^https://[^@\\s]+$",
   "maxLength": 2048,
   "minLength": 10
  },
  "candidate_url": {
   "type": "string",
   "pattern": "^https://[^@\\s]+$",
   "maxLength": 2048,
   "minLength": 10
  },
  "allowed_score_regression": {
   "type": "number",
   "maximum": 1,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-color-contrast-compare-bf798c54/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)
