# Fragment Ancestor Reveal Conditions Analyzer

> Fragment Ancestor Reveal Conditions Analyzer 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-09).

Analyzes a webpage URL to identify ancestor reveal conditions (hidden-until-found elements and closed details) that must be opened along the ancestry path of each fragment-linked target.

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/website-declaration-relations/fragment-ancestor-reveal-conditions?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-09
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fragment-ancestor-reveal-conditions-analyzer-0be7f35d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nXHThltrgXWg7kQ6FltNI

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 fragment-ancestor-reveal-conditions-analyzer-0be7f35d -d '<json body>'
```

Example prompt: Can you check https://example.com/docs/guide for fragment navigation issues — specifically which hidden-until-found or closed details elements need to be revealed along the ancestor path of each anchor target on that page?

## When to prefer this

Choose this endpoint when you need to audit or repair static HTML pages where in-page fragment navigation (#anchor links) may be broken because target elements are hidden inside closed <details> elements or hidden-until-found sections. Particularly useful for documentation sites, FAQs, and accessibility audits where disclosure widgets or progressive disclosure patterns are common.

## Known failure modes

- Invalid or unreachable URL returns an error indicating the page could not be fetched
- Malformed URL format causes input validation failure
- Pages with no fragment targets return an empty result set
- Dynamic content loaded via JavaScript may not be fully analyzed if server-side HTML lacks the required structure
- Very large pages may time out or return partial results

## How this service works

An agent that preserves static fragment navigation needs declared hidden-until-found removal and closed-details opening steps along each linked target ancestry.

## Output

A structured report of each fragment-linked target on the page, listing the ancestry conditions that must be satisfied (e.g. which details elements must be opened, which hidden-until-found attributes must be cleared) for the fragment navigation to successfully reach and display that target.

## 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/fragment-ancestor-reveal-conditions-analyzer-0be7f35d/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)