# Contract Amendments Missingness Co-occurrence Analyzer

> Contract Amendments Missingness Co-occurrence Analyzer is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.020292/call, status unknown (last checked 2026-10-19).

Counts joint null co-occurrences across scope, effective-time, and amount fields in a batch of supplied contract amendment records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020292/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-missingness-co-occurrence-analyzer-f046ee32
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qWrKVWRm6RAE7rG6jHLXh

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-missingness-co-occurrence-analyzer-f046ee32 -d '<json body>'
```

Example prompt: Can you check my batch of up to 32 contract amendment records (labeled as synthetic data) for joint null co-occurrences — specifically how often scope, effective-time, and amount fields are simultaneously missing together?

## When to prefer this

Use this endpoint when you need to systematically quantify how often multiple fields in contract amendment records are jointly absent, without any imputation or inference. It is best suited for data quality auditing, pre-ingestion validation, or compliance review workflows where offline typed metadata analysis of amendment scope, timing, and amount nulls is required. Prefer it over general data profiling tools when you specifically need co-occurrence null counts across these three amendment-specific dimensions.

## Known failure modes

- Batch exceeds 32 records — returns validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — schema validation failure
- Empty records array — minItems constraint violated
- Stale result retrieval after 24-hour window — result no longer available

## How this service works

Count joint nulls in scope, effective-time and amount declarations across supplied amendments. Zero minor units remain supplied; no imputation or completeness inference. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts of joint null occurrences across all pairwise and multi-field combinations of scope, effective-time, and amount declaration fields within the submitted amendment records. No imputation is performed; the result reflects only what was explicitly absent in the supplied data. Results are retained for 24 hours with minimal receipt metadata kept 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-missingness-co-occurrence-analyzer-f046ee32/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)