# DOCX Section Header/Footer Link-to-Previous Effective Parts Resolver

> DOCX Section Header/Footer Link-to-Previous Effective Parts Resolver 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).

Resolves the effective (rendered) header and footer content for each section in a DOCX document, correctly propagating 'link to previous' inheritance across section omissions for first, even, and default part types.

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/F-TD2000-DOCUMENTS-01/docx-section-header-footer-link-to-previous-effective-parts?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/docx-section-header-footer-link-to-previous-effective-parts-resolver-8769be61
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cSJAdes9AR6vwwRpdOVtb

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 docx-section-header-footer-link-to-previous-effective-parts-resolver-8769be61 -d '<json body>'
```

Example prompt: I have a DOCX with 3 sections where even_and_odd headers are enabled; section 1 defines a default header part 'hdr1' and a first-page header 'hdr-first', section 2 omits its header entirely (linking to previous), and section 3 defines only a default header 'hdr3' — can you resolve the effective first, even, and default header and footer parts that would actually render in each section?

## When to prefer this

Use this endpoint when you need to programmatically determine the actual rendered header or footer content for each section of a DOCX file, especially when sections inherit (link to previous) rather than define their own parts. It is the right choice for document rendering pipelines, DOCX validators, and diff tools that need to know exactly which header/footer part is effective at any page position.

## Known failure modes

- Invalid or missing sectionParts data returns a validation error
- Sections array empty or exceeding 32 items rejected
- Part identifiers not present in available_parts may cause resolution errors
- Malformed claim object with section indices out of range
- even_and_odd or title_page flags missing causes schema rejection

## How this service works

Resolve effective first/even/default header and footer parts across section omissions.

## Output

Returns the resolved effective header and footer part identifiers (first, even, default) for each section in the document, correctly accounting for link-to-previous inheritance, even_and_odd page settings, and title_page flags. If a claim is provided, the response indicates whether the claimed effective parts are correct.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "sectionParts"
   ],
   "properties": {
    "sectionParts": {
     "type": "object",
     "required": [
      "data",
      "claim"
     ],
     "properties": {
      "data": {
       "type": "object",
       "required": [
        "even_and_odd",
        "available_parts",
        "sections"
       ],
       "properties": {
        "sections": {
         "type": "array",
         "items": {
          "type": "object",
          "required": [
           "title_page",
           "header",
           "footer"
          ],
          "properties": {
           "footer": {
            "type": "array",
            "items": {
             "type": "object",
             "required": [
              "type",
              "part"
             ],
             "properties": {
              "part": {
               "type": "string",
               "maxLength": 64
              },
              "type": {
               "enum": [
                "first",
                "even",
                "default"
               ]
              }
             },
             "additionalProperties": false
            },
            "maxItems": 3,
            "minItems": 0
           },
           "header": {
            "type": "array",
            "items": {
             "type": "object",
             "required": [
              "type",
              "part"
             ],
             "properties": {
              "part": {
               "type": "string",
               "maxLength": 64
              },
              "type": {
               "enum": [
                "first",
                "even",
                "default"
               ]
              }
             },
             "additionalProperties": false
            },
            "maxItems": 3,
            "minItems": 0
           },
           "title_page": {
            "type": "boolean"
           }
          },
          "additionalProperties": false
         },
         "maxItems": 32,
         "minItems": 1
        },
        "even_and_odd": {
         "type": "boolean"
        },
        "available_parts": {
         "type": "array",
         "items": {
          "type": "string",
          "maxLength": 64
         },
         "maxItems": 32,
         "minItems": 0
        }
       },
       "additionalProperties": false
      },
      "claim": {
       "anyOf": [
        {
         "type": "null"
        },
        {
  
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/docx-section-header-footer-link-to-previous-effective-parts-resolver-8769be61/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)