# Meeting Records — Record Sequence Diff

> Meeting Records — Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035044/call, status unknown (last checked 2026-10-15).

Compares two sets of meeting segment sequences by matching shared segments and computing content digest differences while preserving relative order, using only offline typed non-personal metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/meeting-records/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035044/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meeting-records-record-sequence-diff-617abddf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vFUG0kNBiMlEwaNFvIqIM

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-record-sequence-diff-617abddf -d '<json body>'
```

Example prompt: Can you diff these two meeting segment arrays — the 'before' list has 8 segments and the 'after' list has 10 segments, both marked as synthetic data — and show me which shared segments are preserved in order and where the content digests differ?

## When to prefer this

Use this endpoint when you need to compare two snapshots of a meeting segment sequence to detect additions, deletions, reorderings, or content digest changes, without requiring speaker identification or transcription. Ideal for metadata-only auditing workflows where data is classified as public or synthetic and personal data must not be processed. Prefer this over general diffing tools when the use case specifically involves ordered meeting segment arrays and content digest verification under strict non-personal metadata constraints.

## Known failure modes

- Exceeds maxItems of 32 segments per array — request rejected
- dataClass not set to 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true (const) — request rejected
- Empty arrays on both sides — returns empty diff with no shared segments
- Malformed segment objects with missing digests — may produce incomplete diff
- Network timeout on large segment arrays near the 32-item limit

## How this service works

Compare supplied meeting segment sequence and content digests across two extracts, preserving relative order of shared segments. No speaker identification, transcription or inferred conversational causality. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff of two meeting segment arrays, identifying shared segments and their relative ordering across both sequences, along with content digest comparisons. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No speaker identification, transcription, or conversational inference is included.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meeting-records-record-sequence-diff-617abddf/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)