# HALOWERK Baumarkt Meeting Action Source Timeline

> HALOWERK Baumarkt Meeting Action Source Timeline 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-10).

Analyzes meeting transcript segments to extract and return an action-source timeline identifying who said what and when actions were initiated

## Facts

- Endpoint: POST https://buero.halowerk.com/v1/baumarkt/meeting/action-source-timeline?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-baumarkt-meeting-action-source-timeline-7e85b913
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DnDdX67PjzdZwi-Qm8_kJ

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-baumarkt-meeting-action-source-timeline-7e85b913 -d '<json body>'
```

Example prompt: Take this meeting transcript and build me an action-source timeline — I need to know which speaker triggered each action and exactly when it happened, based on the timestamped segments.

## When to prefer this

Choose this endpoint when you need to attribute specific actions or discussion points to individual meeting speakers with precise timestamps, particularly for post-meeting accountability, automated minutes generation, or compliance audit trails. It supports both raw segment arrays and structured transcript packages, making it flexible for various transcription tool outputs. Best suited for meetings up to 4 hours (14400 seconds) with up to 20,000 segments.

## Known failure modes

- Empty or missing segments array returns validation error
- Segment timestamps exceeding 14400 seconds maximum rejected
- Text fields exceeding 3000 characters per segment cause schema rejection
- transcript_package cues with duration exceeding 1800 seconds fail validation
- Missing required fields (start, end, speaker, text) in segments cause 400 errors
- Payment failure via x402 protocol returns 402 Payment Required
- Overlapping or out-of-order timestamps may produce unexpected timeline ordering

## How this service works

Create a task timeline ordered by source timestamps with stable tie handling. Reuses exactly one existing qualified meeting-notes request. Supplied source goes to the existing Groq model in the USA; existing processor disclosure and cost/margin retained. Notes quotes/owners/deadlines are verified by the unchanged motor first. Extra rules are deterministic; no semantic deadline resolution or specialist advice. Base motor quote plus0.001USDC; article fails before settlement if the motor fails.

## Output

A JSON response containing a chronological action-source timeline derived from the meeting transcript, mapping each identified action or notable event to its originating speaker and the corresponding timestamp range within the meeting.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "segments": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "start",
     "end",
     "speaker",
     "text"
    ],
    "properties": {
     "end": {
      "type": "number",
      "maximum": 14400,
      "exclusiveMinimum": 0
     },
     "text": {
      "type": "string",
      "maxLength": 3000,
      "minLength": 1
     },
     "start": {
      "type": "number",
      "maximum": 14400,
      "minimum": 0
     },
     "speaker": {
      "type": [
       "string",
       "null"
      ],
      "maxLength": 80,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20000,
   "minItems": 1
  },
  "transcript_package": {
   "type": "object",
   "required": [
    "cues",
    "media"
   ],
   "properties": {
    "cues": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "start",
       "end",
       "speaker",
       "text"
      ],
      "properties": {
       "end": {
        "type": "number",
        "maximum": 1801,
        "exclusiveMinimum": 0
       },
       "text": {
        "type": "string",
        "maxLength": 3000,
        "minLength": 1
       },
       "start": {
        "type": "number",
        "maximum": 1801,
        "minimum": 0
       },
       "speaker": {
        "type": [
         "integer",
         "null"
        ],
        "maximum": 20000,
        "minimum": 0
       }
      }
     },
     "maxItems": 20000,
     "minItems": 1
    },
    "media": {
     "type": "object",
     "required": [
      "duration_seconds"
     ],
     "properties": {
      "duration_seconds": {
       "type": "number",
       "maximum": 1800,
       "exclusiveMinimum": 0
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-baumarkt-meeting-action-source-timeline-7e85b913/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)