# HALOWERK laufwerk – Compare Console Errors Between URLs

> HALOWERK laufwerk – Compare Console Errors Between URLs 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 browser console errors between a baseline URL and a candidate URL, returning a quality regression score and error diff.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/quality/compare-errors-in-console?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-compare-console-errors-between-urls-b819fbf9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rDnYXpKOgnqPnaEFOcIWa

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-compare-console-errors-between-urls-b819fbf9 -d '<json body>'
```

Example prompt: Compare browser console errors between https://www.myapp.com (baseline) and https://staging.myapp.com (candidate) and flag any regression — allow up to 0.1 score regression before failing.

## When to prefer this

Use this endpoint when you need an automated, scored comparison of browser console errors between two specific URLs — ideal for CI/CD quality gates, pre-deployment checks, or A/B variant health comparisons. Prefer it over manual browser testing or generic scraping when you want a numeric regression signal with a configurable tolerance threshold.

## Known failure modes

- Invalid or unreachable baseline_url returns an error response
- Invalid or unreachable candidate_url returns an error response
- URL does not match required https:// pattern — validation error
- allowed_score_regression outside 0–1 range causes schema validation failure
- Network timeout loading one or both URLs
- Ambiguous or empty JSON response if the page has no console output

## How this service works

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

## Output

A JSON response containing a comparison of browser console errors found on the baseline URL versus the candidate URL, including an error quality score for each, whether the allowed regression threshold was exceeded, and details of any new or worsened errors on the candidate.

## 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-compare-console-errors-between-urls-b819fbf9/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)
