# Contract Amendments — Duplicate Record Identities

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

Groups repeated contract amendment IDs by revision digest to distinguish identical duplicate rows from conflicting revisions, without making validity judgments.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/duplicate-record-identities?utm_source=zero.xyz
- Price: $0.010292/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-duplicate-record-identities-d7e45bda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8TO4RCoOE2Qe7pu0tJ-x7

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-duplicate-record-identities-d7e45bda -d '<json body>'
```

Example prompt: I have a batch of up to 32 contract amendment records marked as synthetic data — can you group them by revision digest so I can see which repeated amendment IDs are exact duplicates versus conflicting revisions?

## When to prefer this

Choose this endpoint when you need to programmatically distinguish true duplicate amendment rows (identical content) from conflicting revisions sharing the same amendment ID, without any downstream validity assessment. It is best suited for offline, typed metadata workflows on public or synthetic data where personal data is absent. Prefer this over generic deduplication tools when the domain is specifically contract amendments and you need revision-digest-level grouping rather than simple field-matching.

## Known failure modes

- Input array exceeds 32 records — request rejected
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- Empty records array (fewer than 1 item) — validation error
- Downstream timeout if digest computation is slow on large records
- Result expired after 24-hour retention window — receipt only recoverable for 90 days

## How this service works

Group repeated amendment IDs by revision digest, distinguishing identical duplicate rows from conflicting revisions. No amendment validity judgment. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns amendment records grouped by revision digest, with each group labeled to indicate whether repeated amendment IDs represent identical duplicate rows or conflicting revisions. No validity judgment is made on the amendments themselves. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "records": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "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-duplicate-record-identities-d7e45bda/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)