# Contract Amendments — Schema Directionality

> Contract Amendments — Schema Directionality is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035025/call, status unknown (last checked 2026-10-19).

Compares before/after contract amendment schema projections to detect removed fields, changed types, new requirements, and narrowed nullability between tenant/contract frames.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/schema-directionality?utm_source=zero.xyz
- Price: $0.035025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/contract-amendments-schema-directionality-616322f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vjwcqnl_SuxIHsVVrANTn

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 contract-amendments-schema-directionality-616322f7 -d '<json body>'
```

Example prompt: Compare these two contract amendment schema snapshots — the 'before' has 5 projection fields and the 'after' has 4 — and tell me which fields were removed, which types changed, and whether any fields became newly required or had their nullability narrowed. Data class is public.

## When to prefer this

Choose this endpoint when you need a precise, typed comparison of contract amendment schema projections to catch structural breaking changes — specifically removed fields, type mutations, new required fields, and narrowed nullability — between two versioned states. It is scoped exclusively to offline, nonpersonal, public or synthetic metadata and does not perform legal interpretation or general schema subtyping analysis.

## Known failure modes

- before array is empty or missing (minItems:1 violated) — validation error
- after or before array exceeds 32 items — request rejected
- dataClass not set to 'public' or 'synthetic' — enum validation error
- nonpersonalMetadata is not exactly true — const constraint violation
- beforeFrame or afterFrame objects are malformed or missing required structure — schema error
- personal data included in payload — rejected by data class policy

## How this service works

Compare closed amendment projection fields and tenant/contract frames for removed fields, changed types, new requirements and narrowed nullability. No general schema subtyping or legal interpretation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured report listing schema directionality changes between the before and after amendment projections: fields present in the before set but absent in the after (removals), fields whose types changed, fields that became newly required, and fields where nullability was narrowed. 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": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "afterFrame": {
   "type": "object"
  },
  "beforeFrame": {
   "type": "object"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/contract-amendments-schema-directionality-616322f7/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)