# Meeting Records - Export Semantic Parity

> Meeting Records - Export Semantic Parity is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.039295/call, status unknown (last checked 2026-11-04).

Compares two sets of closed nonpersonal meeting record exports by stable ID, agenda, revision, digest, offset, and owner-role labels, ignoring row order and without performing natural-language equivalence or agreement verification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/meeting-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039295/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meeting-records-export-semantic-parity-bfd33296
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sVnq0l9naFKsr9OW65QZz

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-export-semantic-parity-bfd33296 -d '<json body>'
```

Example prompt: Compare these two batches of closed meeting records — up to 32 items each, using public data class, labeled 'Q2 Audit Check' — and tell me if they are semantically equivalent by stable ID, agenda, revision, digest, offset, and owner-role labels, ignoring row order.

## When to prefer this

Use this endpoint when you need a deterministic, row-order-agnostic structural comparison of two closed nonpersonal meeting record exports — particularly when auditing migrations, validating synthetic datasets, or checking for field-level drift in agenda, revision, digest, offset, or owner-role labels. Not appropriate when you need natural-language agreement analysis, personal data processing, or live meeting content verification.

## Known failure modes

- Arrays exceeding 32 items rejected with validation error
- dataClass value outside 'public' or 'synthetic' enum rejected
- exportLabel missing or exceeding 200 characters returns schema error
- nonpersonalMetadata not set to true causes request rejection
- Empty or malformed record objects may yield incomplete comparison
- Payment failure returns 402 status with no result

## How this service works

Compare closed nonpersonal meeting decision projections by stable ID, agenda, revision, digest, offset and owner-role labels. Ignores row order; no natural-language equivalence or agreement verification. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured semantic parity report indicating whether the before and after meeting record arrays match across stable ID, agenda, revision, digest, offset, and owner-role label dimensions. Highlights any field-level discrepancies. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## 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"
  },
  "exportLabel": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meeting-records-export-semantic-parity-bfd33296/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)