# HALOWERK buerowerk Meeting Deadline Token Register Snapshot Compare

> HALOWERK buerowerk Meeting Deadline Token Register Snapshot Compare is a paid API for AI agents from buero.halowerk.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-18).

Compares a new meeting transcript/notes snapshot against a baseline to detect changes in topics, decisions, action items, deadlines, and open questions

## Facts

- Endpoint: POST https://buero.halowerk.com/v1/baumarkt/meeting/deadline-token-register/snapshot-compare?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-buerowerk-meeting-deadline-token-register-snapshot-compare-3d4dd890
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ydV9NBhtbPy6GBEEi6hDW

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-buerowerk-meeting-deadline-token-register-snapshot-compare-3d4dd890 -d '<json body>'
```

Example prompt: Compare my original meeting notes from last Tuesday's sprint planning with the updated transcript I just got — same baseline notes with the summary, topics, decisions, action items owned by Sarah and Jake, and the new segments — and tell me what changed in terms of deadlines, owners, and any new open questions.

## When to prefer this

Choose this endpoint when you need to programmatically diff two versions of a structured meeting record — especially when tracking changes to action items, deadlines, owners, decisions, or open questions between an original baseline and a new transcript. Prefer it over generic text-diff tools when you need structured, meeting-aware change detection that understands the schema of meeting notes (topics, decisions, action items with owners and due dates).

## Known failure modes

- Missing required 'summary' field in baseline notes returns validation error
- Baseline source must include either 'segments' or 'transcript_package' but not neither — omitting both returns schema error
- Action items missing required fields (text, quote, segment_index, owner, due_raw) cause request rejection
- Exceeding maxItems (30) on any array field results in validation failure
- Payment not provided or insufficient USDC triggers x402 payment required response
- Malformed segment references cause comparison to fail silently or return partial results

## How this service works

HALOWERK buerowerk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

A JSON object containing a comparison between the baseline meeting notes and the new transcript/segments, highlighting changes in topics, decisions, action items (including owner and deadline changes), summary drift, and open questions that were added, removed, or modified.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "baseline": {
   "type": "object",
   "required": [
    "source",
    "notes"
   ],
   "properties": {
    "notes": {
     "type": "object",
     "required": [
      "summary",
      "topics",
      "decisions",
      "action_items",
      "open_questions"
     ],
     "properties": {
      "topics": {
       "type": "array",
       "items": {
        "$ref": "#/$defs/ma5dd9d00ff"
       },
       "maxItems": 30
      },
      "summary": {
       "type": "array",
       "items": {
        "$ref": "#/$defs/ma5dd9d00ff"
       },
       "maxItems": 30,
       "minItems": 1
      },
      "decisions": {
       "type": "array",
       "items": {
        "$ref": "#/$defs/ma5dd9d00ff"
       },
       "maxItems": 30
      },
      "action_items": {
       "type": "array",
       "items": {
        "type": "object",
        "required": [
         "text",
         "quote",
         "segment_index",
         "owner",
         "due_raw"
        ],
        "properties": {
         "text": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 1
         },
         "owner": {
          "type": [
           "string",
           "null"
          ],
          "maxLength": 80
         },
         "quote": {
          "type": "string",
          "maxLength": 3000,
          "minLength": 1
         },
         "due_raw": {
          "type": [
           "string",
           "null"
          ],
          "maxLength": 3000
         },
         "segment_index": {
          "type": "integer",
          "minimum": 0
         }
        }
       },
       "maxItems": 30
      },
      "open_questions": {
       "type": "array",
       "items": {
        "$ref": "#/$defs/ma5dd9d00ff"
       },
       "maxItems": 30
      }
     }
    },
    "source": {
     "type": "object",
     "oneOf": [
      {
       "required": [
        "segments"
       ]
      },
      {
       "required": [
        "transcript_package"
       ]
      }
     ],
     "required": [],
     "properties": {
      "segments": {
       "$ref": "#/$defs/mbdf0d3bb9b"
      },
      "transcript_package": {
       "$ref": "#/$defs/m81f20e3330"
      }
     },
     "additionalProperties": false
    }
   }
  },
  "segments": {
   "$ref": "#/$defs/mbdf0d3bb9b"
  },
  "transcript_package": {
   "$ref": "#/$defs/m81f20e3330"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-buerowerk-meeting-deadline-token-register-snapshot-compare-3d4dd890/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)