Back to Browse
Meeting Records - Export Semantic Parity
x402
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.
Price / call$0.039295
Success—
StatusUnknown
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.
Example use cases
Audit meeting record export consistency
“I have two exports of our board meeting records from before and after a system migration — can you compare them using public data class, labeled 'Migration Parity Check', and tell me if the stable IDs, agendas, revisions, digests, offsets, and owner-role labels all match, ignoring any reordering?”
Validate synthetic meeting data integrity
“Check whether these two synthetic meeting record snapshots — up to 30 records each — are semantically identical by stable ID and owner-role labels; label the export 'Synthetic Dataset Validation' and make sure you're only comparing nonpersonal metadata.”
Detect agenda or revision drift between record versions
“I need to know if any agenda items, revision numbers, or digest values changed between my two sets of closed meeting records — label this comparison 'Sprint Review Drift Check' using public data class, and tell me exactly which fields differ.”
Technical details
Endpoint
POSThttps://www.mahastrategies.com/api/v1/context/meeting-records/export-semantic-parity?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| after | array | |
| before | array | |
| dataClass | string | |
| exportLabel | string | |
| nonpersonalMetadata | boolean |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"