# API Contracts Missingness Co-occurrence Analyzer

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

Counts joint missing owner, input schema, and output schema pins across a batch of HTTP contract metadata records to identify co-occurring declaration gaps.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020303/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-missingness-co-occurrence-analyzer-bfe26563
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eI009NXu8lqZ6giIxBWWA

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

Example prompt: Can you check these 10 API contract metadata records — all public, nonpersonal — and tell me how many are jointly missing the owner declaration along with their input or output schema pins at the same time?

## When to prefer this

Use this endpoint when you need to quantify co-occurring declaration gaps — specifically joint absences of owner, input schema, and output schema pins — across a batch of HTTP contract metadata records. It is distinct from single-field required-field checks (use the Required-field coverage sibling for that) and is best suited for governance audits, data quality pipelines, and pre-publication reviews where pattern-level missingness analysis across multiple contracts matters. Supports only public or synthetic, nonpersonal metadata.

## Known failure modes

- Batch exceeds 32 contracts — request rejected with validation error
- nonpersonalMetadata is not set to true — request rejected
- dataClass not set to 'public' or 'synthetic' — invalid enum error
- Empty contracts array (minItems:1 not met) — validation failure
- Malformed contract objects in array — parsing error returned

## How this service works

Count joint missing owner, input and output schema pins in HTTP contract metadata. An incomplete declaration does not establish an unavailable or unsafe runtime service. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts and patterns of jointly missing metadata fields (owner, input schema pin, output schema pin) across the submitted HTTP contract records, indicating how frequently these absences co-occur. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contracts": {
   "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/api-contracts-missingness-co-occurrence-analyzer-bfe26563/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)