# Halowerk Native Stacking Context Paint Order Contraction Detector

> Halowerk Native Stacking Context Paint Order Contraction Detector is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-04).

Analyzes a web page URL to detect and report native CSS stacking-context forest structure and DOM sibling-context paint order inversions for layering debugging.

## Facts

- Endpoint: POST https://detect.halowerk.com/u/offline-native-stacking-context-paint-order-contraction?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-native-stacking-context-paint-order-contraction-detector-c9c0c114
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZXjfkRwlnoR0q3TZMJTfo

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-native-stacking-context-paint-order-contraction-detector-c9c0c114 -d '<json body>'
```

Example prompt: Can you analyze https://example.com/dashboard for native CSS stacking-context conflicts and paint order inversions so I can figure out why my modal is rendering behind the sidebar?

## When to prefer this

Use this endpoint when debugging CSS layering issues where z-index behaves unexpectedly, specifically when you need a programmatic, offline-compatible breakdown of the full stacking-context tree and paint-order inversions for a given page URL. Prefer this over manual DevTools inspection when you need structured, machine-readable output for automated layering audits.

## Known failure modes

- Invalid or unreachable URL returns an error indicating the page could not be fetched
- Pages with heavy JavaScript rendering may produce incomplete stacking context trees if JS has not fully executed
- URLs requiring authentication will likely return incomplete or no stacking context data
- Malformed URI input results in a 400-level validation error
- Rate limiting or payment failure returns a 402 or 429 response

## How this service works

A layering debugger needs the native stacking-context forest and DOM sibling-context paint inversions in this offline state.

## Output

Returns a structured report of the native CSS stacking-context forest for the given URL, including which DOM elements establish new stacking contexts, their hierarchy, and any detected paint-order inversions between sibling contexts that could cause layering bugs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "maxLength": 2048
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-native-stacking-context-paint-order-contraction-detector-c9c0c114/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)