# Halowerk Buero Doc-Merge (Three-Way Document Merger)

> Halowerk Buero Doc-Merge (Three-Way Document Merger) is a paid API for AI agents from buero.halowerk.com, paid per call via x402, $0.004/call, status down (last checked 2026-09-16).

Performs a three-way diff3 merge of documents — a common base and two derived versions — resolving conflicts by rule and returning a single merged document.

## Facts

- Endpoint: POST https://buero.halowerk.com/v1/doc-merge
- Price: $0.004/call
- Payment: x402
- Status: down
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-buero-doc-merge-three-way-document-merger-87334f7d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_quY8DYw22cLDW3NlxMSTO

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-buero-doc-merge-three-way-document-merger-87334f7d -d '<json body>'
```

Example prompt: Merge these three documents for me: the original contract draft is the base, then I have my revised version and the legal team's revised version — use paragraph-level merging and give me back one clean combined document.

## When to prefer this

Choose this endpoint when you have a known common ancestor document and two independently modified versions that need to be reconciled into one — the classic three-way merge scenario from version control. It handles rich document formats (PDF, DOCX, ODT, HTML, Markdown) natively, making it ideal for office workflows where binary formats are common. Prefer it over simple two-way diff tools when you need conflict resolution by rule rather than manual intervention.

## Known failure modes

- Unresolvable conflicts if both versions change the same passage differently and no automatic rule applies
- Unsupported file format or malformed base64 input causing a parse error
- Inaccessible public URL returning a fetch error
- Extremely large documents exceeding size or processing limits
- Network timeout on slow upstream URL fetches

## How this service works

Takes three documents — the common base and the two versions derived from it — as text, public URLs or inline base64, reads PDF, DOCX, ODT, HTML and Markdown, and returns one merged document. The procedure is diff3 over paragraphs, or over lines if you ask for that: each version is first compared against the base with a Myers shortest-edit-script, the two comparisons together yield the passages that are identical in all three, and each region between them is resolved by rule.

## Output

A single merged document produced by resolving the three-way diff between the base and two derived versions. Identical passages across all three are kept as-is; differing regions are resolved automatically by rule. Output is a clean, unified document in text form.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-buero-doc-merge-three-way-document-merger-87334f7d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from buero.halowerk.com](https://www.zero.xyz/host/buero.halowerk.com/llms.txt)