# Reaction Records Schema Directionality

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

Compares closed export-field schema directionality for supplied reaction records, identifying breaking vs. non-breaking field changes without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035169/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-schema-directionality-e2e36caa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VKJiNLQxrMXfHyRirUKLn

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-schema-directionality-e2e36caa -d '<json body>'
```

Example prompt: Can you check if my reaction record schema changes are breaking? I'm moving from a 'public' data class and removing two fields — compare the before list [fieldA, fieldB, fieldC] against the after list [fieldA, fieldC], with nonpersonalMetadata set to true and consumerAllowsExtraFields false.

## When to prefer this

Choose this endpoint when you need a fast, lightweight check of closed export-field directionality for reaction record schemas — particularly when comparing versioned field lists to detect breaking changes before deployment. Prefer this over general schema evolution tools when your data is explicitly scoped to public or synthetic dataClass and you need per-record analysis rather than semantic equivalence proofs.

## Known failure modes

- Empty before array (minItems:1 violated) returns validation error
- before or after arrays exceeding 32 items are rejected
- Invalid dataClass value (not 'public' or 'synthetic') causes schema rejection
- nonpersonalMetadata not set to true (const:true) causes request rejection
- Malformed field arrays cause parse errors

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a schema directionality analysis indicating whether changes between the before and after field sets represent breaking or non-breaking transitions, with field-level classification for each change. Does not perform independent certification — results reflect the supplied record analysis only.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reaction-records-schema-directionality-e2e36caa/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)