# Halowerk Büro Meeting Actions Extractor

> Halowerk Büro Meeting Actions Extractor is a paid API for AI agents from buero.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-12).

Extracts action items, owners, deadlines, decisions, and open questions from a meeting transcript, with each entry verified against a verbatim passage in the source text.

## Facts

- Endpoint: POST https://buero.halowerk.com/v1/meeting-actions?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-b-ro-meeting-actions-extractor-fcf38507
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PyywQ4mjCik6CFThtugU0

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-b-ro-meeting-actions-extractor-fcf38507 -d '<json body>'
```

Example prompt: Here's the transcript from today's product sync — can you pull out all the action items with who owns each one and when it's due, all the decisions that were made, and any questions that didn't get resolved? Use this URL: https://drive.example.com/transcript.txt

## When to prefer this

Choose this endpoint when you need structured, accountable extraction of meeting outcomes — specifically action items with owners and deadlines, formal decisions, and open questions — and you need each extracted item to be traceable back to a verified verbatim passage in the source transcript. Prefer it over generic summarization endpoints when auditability and attribution are important, or when you need to automatically populate task management systems from meeting transcripts.

## Known failure modes

- Transcript URL is not publicly accessible — returns an access error
- Base64 payload is malformed or too large — returns a parsing error
- No clear action items, decisions, or questions found in the transcript — returns empty lists
- Verbatim passage cannot be matched in the transcript — entry is excluded or flagged
- Transcript is in an unsupported format or language — may return incomplete results

## How this service works

Takes a transcript as text, a public URL or inline base64 and returns what follows from the meeting: the tasks, who is responsible, by when, the decisions that were actually taken, and the questions that stayed open. Every single entry carries the verbatim passage it was drawn from, and that passage is looked up in the transcript before the answer goes out — an exact match or a match after whitespace is normalised.

## Output

A structured response containing: a list of action items each with the responsible party, due date, and verbatim transcript passage it was drawn from; a list of decisions made with sourcing passages; and a list of open/unresolved questions, all verified against exact or whitespace-normalized matches in the original transcript.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transcript": {
   "type": "object",
   "properties": {
    "url": {
     "type": "string",
     "maxLength": 2048,
     "description": "Public http(s) URL of a PDF, DOCX, ODT, HTML or text file. Private and local addresses are refused."
    },
    "text": {
     "type": "string",
     "maxLength": 200000,
     "description": "The text directly. Cheapest and clearest — its length is billed as counted here."
    },
    "format": {
     "enum": [
      "auto",
      "pdf",
      "docx",
      "odt",
      "html",
      "markdown",
      "rtf",
      "text"
     ],
     "type": "string",
     "default": "auto",
     "description": "Override the detected format. \"auto\" reads it from the bytes."
    },
    "filename": {
     "type": "string",
     "maxLength": 260,
     "description": "Only consulted when the bytes carry no recognisable signature."
    },
    "content_base64": {
     "type": "string",
     "maxLength": 4000000,
     "description": "The file inline, base64."
    }
   },
   "description": "The meeting transcript. Exactly one of text, url or content_base64.",
   "additionalProperties": false
  },
  "document_chars": {
   "type": "integer",
   "maximum": 24000,
   "minimum": 1,
   "description": "Only needed when the transcript arrives by url or content_base64: its length in characters, which is what you are billed for. A longer text is refused with its real length and nothing is charged."
  },
  "reference_date": {
   "type": "string",
   "maxLength": 40,
   "description": "The day the meeting took place, ISO 8601. Without it, relative deadlines like \"next Friday\" are returned as spoken and marked unresolved rather than guessed."
  },
  "include_unverified": {
   "type": "boolean",
   "default": true,
   "description": "Also return entries whose quote could not be located in the transcript, clearly marked."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-b-ro-meeting-actions-extractor-fcf38507/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)