# Contract Amendments — Record Sequence Diff

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

Compares two ordered sequences of contract amendment records, detecting identity differences, effective-time declaration changes, and relative reordering among shared records without inferring legal precedence.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035026/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-record-sequence-diff-2b9299cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IH2YnxwXg19frUo4qUsW0

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-record-sequence-diff-2b9299cf -d '<json body>'
```

Example prompt: Compare these two contract amendment sequences — here's the before list and here's the after list — and tell me which records changed identity or effective-time declarations, and whether any shared records were reordered. Mark the data class as public.

## When to prefer this

Choose this endpoint when you need a precise, offline structural comparison of two ordered contract amendment sequences — specifically to detect identity shifts, effective-time declaration changes, and reordering among shared records — without needing legal precedence inference or persistent storage. Ideal for compliance auditing, contract pipeline validation, and amendment version control workflows where data must be classified as public or synthetic and personally identifiable information is absent.

## Known failure modes

- Input arrays exceeding 32 items return a validation error
- nonpersonalMetadata must be set to true — omission or false value will be rejected
- Invalid dataClass value (anything other than 'public' or 'synthetic') causes a schema error
- Empty before and after arrays with no shared records may return a trivially empty diff
- Stale results beyond 24-hour retention window are no longer accessible

## How this service works

Compare supplied amendment revision sequences by identity, effective-time declarations and relative order among shared records. Added entries do not by themselves imply reordering; no legal precedence inference. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff report identifying: records present only in the before or after sequence (additions/removals), records whose identity or effective-time declarations changed, and records shared between sequences that appear in a different relative order. Does not infer legal precedence. Results are retained for 24 hours; minimal receipt metadata 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": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/contract-amendments-record-sequence-diff-2b9299cf/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)