# Meeting Records - Unit-Label Consistency Checker

> Meeting Records - Unit-Label Consistency Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012295/call, status unknown (last checked 2026-10-23).

Validates that meeting segment offset, duration, and count units match their declared quantities and checks for repeated metric identity conflicts in meeting record metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/meeting-records/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012295/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meeting-records-unit-label-consistency-checker-d4d48483
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YaUf34Q_pYCP3ejU0R4xL

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 meeting-records-unit-label-consistency-checker-d4d48483 -d '<json body>'
```

Example prompt: Check these meeting segment measurements for unit-label consistency — they're synthetic, non-personal metadata — and flag any mismatches between declared units and quantities or any repeated metric identities.

## When to prefer this

Use this endpoint when you need a lightweight, offline unit-label consistency check on typed meeting segment metadata (offsets, durations, counts) without any transcript inspection, speech timing analysis, or physical unit conversion. It is ideal for data quality pipelines that need to validate declared units match stated quantities and detect repeated metric identities before downstream processing, using only non-personal metadata.

## Known failure modes

- Measurements array is empty or exceeds 32 items — returns validation error
- dataClass not set to 'public' or 'synthetic' — rejected by schema
- nonpersonalMetadata not set to true — request refused
- Malformed measurement objects lacking required unit/quantity fields — parsing error
- Network timeout for large measurement arrays — no partial result

## How this service works

Check meeting segment offset/duration/count units against their declared quantities and repeated metric identities. No guessed conversion, transcript inspection or speech timing validation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A validation report indicating whether meeting segment offset, duration, and count unit labels are consistent with their declared quantities, plus a list of any repeated metric identity conflicts found. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No transcript content, speech timing, or guessed conversions are included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "measurements": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meeting-records-unit-label-consistency-checker-d4d48483/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)