# Neural Interface Records - Schema Directionality Comparator

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

Compares closed export-field schema directionality for supplied neural interface records, flagging structural differences between before and after record sets.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/neural-interface-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035229/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/neural-interface-records-schema-directionality-comparator-f4dbfc86
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mkrNUMECSmAx4FKAEMnC-

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 neural-interface-records-schema-directionality-comparator-f4dbfc86 -d '<json body>'
```

Example prompt: Compare the schema directionality for these neural interface records — before has up to 32 entries and after has up to 32 entries, using the 'public' data class with nonpersonal metadata only, and let the consumer accept extra fields.

## When to prefer this

Choose this endpoint when you need to compare closed export-field schema directionality between two snapshots of neural interface records, particularly when validating structural consistency of before/after record states with either public or synthetic data classes. Prefer this over generic schema diff tools when the records are neural interface records and you need export-field-specific directionality analysis rather than raw field-level diffing.

## Known failure modes

- before array must have at least 1 item — empty before arrays are rejected
- after array exceeds 32-item limit — request fails with validation error
- dataClass must be exactly 'public' or 'synthetic' — other values are rejected
- nonpersonalMetadata must be exactly true (const) — false or missing causes failure
- Schema mismatch or malformed record structure may return analysis error
- Network or provider downtime returns 5xx error

## How this service works

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

## Output

Returns a comparison of schema directionality between the before and after record arrays, indicating whether export fields maintain consistent direction, any structural divergences detected, and whether the supplied records conform to the closed export-field specification. This is a supplied-record analysis, not an independent certification.

## 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/neural-interface-records-schema-directionality-comparator-f4dbfc86/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)