# Reaction Records Export Semantic Parity

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

Compares two sets of parsed typed reaction record projections for semantic equivalence, preserving pins and scope while ignoring ordering differences.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039316/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reaction-records-export-semantic-parity-3e28f164
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OO8CsbDlC0qqcvlkkK8aG

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 reaction-records-export-semantic-parity-3e28f164 -d '<json body>'
```

Example prompt: Can you check if these two sets of reaction record projections are semantically equivalent — here are up to 32 records in the 'before' list and up to 32 in the 'after' list, using the 'synthetic' data class with nonpersonal metadata only? I need to know if all pins and scope are preserved even if the order changed.

## When to prefer this

Use this endpoint when you need to verify semantic equivalence between two versions of reaction record projections and care about pin and scope preservation but not raw byte ordering. Prefer this over raw diff tools when typed projection semantics matter, and over general-purpose diff APIs when working specifically with reaction/dataset/method/revision record structures on the Maha Strategies platform.

## Known failure modes

- Array exceeds 32 items — request rejected with validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- Malformed record objects in before/after arrays — parse error returned
- Empty or missing required fields — 400 bad request

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for dataset/reaction/method/revision Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment comparing the before and after reaction record projection arrays, indicating whether all pins and scope are preserved and highlighting any semantic mismatches — without raw-byte comparison or artifact certification.

## 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/reaction-records-export-semantic-parity-3e28f164/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)