# Contract Amendments — Unit-Label Consistency Checker

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

Detects multiple conflicting currency declarations for the same monetary field within contract amendment records, using only typed metadata without currency conversion or payment-term interpretation.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012292/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-unit-label-consistency-checker-cb004af4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oKlNDSYsn-33mTRefTNn_

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-unit-label-consistency-checker-cb004af4 -d '<json body>'
```

Example prompt: Can you check this batch of contract amendment records for currency label conflicts — I need to know if any monetary field has been declared in more than one currency across the records? The contract ID is CNT-2024-0892, this is synthetic data, and nonpersonalMetadata is true.

## When to prefer this

Choose this endpoint when you need a lightweight, offline metadata-only check for currency label consistency within contract amendment records — specifically when you do NOT need currency conversion, exchange-rate lookups, or payment-term interpretation. Ideal for document QA pipelines, compliance pre-checks, and legal review workflows where the goal is purely to detect ambiguous or conflicting unit declarations on monetary fields using only structured typed metadata.

## Known failure modes

- Batch too large: array exceeds 32 items, request rejected
- Missing required nonpersonalMetadata:true field causes validation error
- Invalid dataClass value outside enum ['public','synthetic'] causes rejection
- Missing or empty records array (minItems:1 not met)
- No currency conflicts found returns empty inconsistency list (not an error)
- Retained result expired after 24-hour window, requiring resubmission

## How this service works

Detect multiple declared currencies for the same contract monetary field without converting currencies or interpreting payment terms. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured report identifying which monetary fields within the contract amendment records have been declared with multiple, conflicting currency labels, along with field-level consistency flags. No currency conversion or payment-term interpretation is performed — output is limited to typed metadata analysis. 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"
  },
  "contractId": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/contract-amendments-unit-label-consistency-checker-cb004af4/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)