# Flex Cross-Band and Order Reconstruction Detector

> Flex Cross-Band and Order Reconstruction 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 URL to compute realized cross-axis flex bands and order-modified item sequences after native browser layout, replacing nominal flex-basis simulations.

## Facts

- Endpoint: POST https://detect.halowerk.com/u/offline-used-flex-cross-band-and-order-reconstruction?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/flex-cross-band-and-order-reconstruction-detector-678d6adc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WATqmOyloV8bBSedrnd2g

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 flex-cross-band-and-order-reconstruction-detector-678d6adc -d '<json body>'
```

Example prompt: Can you reconstruct the actual flex cross-axis bands and order-modified item sequences from this page — I need the native realized layout, not a simulated flex-basis estimate: https://example.com/my-flex-layout

## When to prefer this

Choose this endpoint when you need the actual native-layout output of CSS flexbox containers — specifically the cross-axis band assignments and order-modified item sequences — rather than a simulated or nominal flex-basis estimate. It is most useful during flex layout migration, refactoring, or agent-driven layout reconstruction workflows where accuracy against browser rendering is required.

## Known failure modes

- URL is unreachable or returns a non-200 status — layout cannot be fetched
- Page uses dynamic JS rendering that is not executed, resulting in incomplete layout data
- URL does not contain any flex containers — returns empty or null band data
- Malformed URL input causes validation failure before processing
- Page requires authentication, blocking layout analysis

## How this service works

A flex migration agent needs realized cross-start bands and order-modified item sequences after native layout, rather than a nominal source flex-basis simulation.

## Output

Returns the realized flex cross-axis band groupings and order-modified item sequences as computed after native layout, including actual flex-basis positions rather than nominal simulated values, structured for use in migration or reconstruction workflows.

## 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/flex-cross-band-and-order-reconstruction-detector-678d6adc/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)