# Glossary Records - Missingness Co-occurrence

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

Counts paired co-occurring missing fields (owner, revision, and content pins) across glossary records without treating missing values as matches, for vocabulary/term/language/namespace/revision-pinned glossary data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/glossary-records/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020342/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glossary-records-missingness-co-occurrence-84ec0abb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VnL5HRiLceKG9FRevhYz3

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 glossary-records-missingness-co-occurrence-84ec0abb -d '<json body>'
```

Example prompt: Can you audit these glossary records (up to 32 rows, public data, no personal metadata) and count how often the owner pin, revision pin, and content pin fields are simultaneously missing — without treating a blank as a match?

## When to prefer this

Choose this endpoint when you need to quantify co-occurring missingness across owner, revision, and content pin fields in glossary or vocabulary records, specifically without silently equating a missing value to a match. Best for data quality audits on pinned glossary datasets (vocabulary, term, language, namespace, revision-pinned) using public or synthetic data with no personal metadata.

## Known failure modes

- rows array empty or exceeds 32 items — validation error returned
- dataClass not one of 'public' or 'synthetic' — rejected with enum error
- nonpersonalMetadata not set to true (const constraint) — request rejected
- malformed row objects missing expected glossary fields — partial or error result
- upstream service unavailable — 5xx error

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for vocabulary/term/language/namespace/revision-pinned glossary Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns co-occurrence counts of paired missing fields (owner pin, revision pin, content pin) across the submitted glossary rows, clearly distinguishing absent values from matching values and reporting which field pairs are simultaneously missing most often.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "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/glossary-records-missingness-co-occurrence-84ec0abb/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)