# Tabular Records - Missingness Co-occurrence Counter

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

Counts pairwise co-occurrences of absent required-column declarations across bounded row-presence metadata for offline typed nonpersonal tabular records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tabular-records/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020305/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tabular-records-missingness-co-occurrence-counter-62e52fc8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kr0fI-nd23lE_sTaeNggi

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 tabular-records-missingness-co-occurrence-counter-62e52fc8 -d '<json body>'
```

Example prompt: Can you count pairwise missingness co-occurrences across these 20 rows of synthetic tabular metadata where the required columns are 'id', 'timestamp', 'category', and 'value'?

## When to prefer this

Choose this endpoint when you need to quantify pairwise co-occurrences of missing required columns in bounded offline nonpersonal tabular metadata (up to 32 rows, up to 14 required columns), without any raw-cell imputation, population inference, or live database access. Prefer this over general-purpose data profiling tools when you specifically need fast, typed, offline co-occurrence counting on synthetic or public row-presence metadata.

## Known failure modes

- rows array exceeds 32 items — request rejected
- requiredColumns exceeds 14 entries — request rejected
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- empty rows or requiredColumns arrays — request rejected
- submission of personally identifiable data — policy violation

## How this service works

Count pairwise absent required-column declarations in bounded row-presence metadata. No raw cells, missing-value imputation, population inference or database query. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns pairwise counts of how often each combination of required columns is simultaneously absent across the submitted row metadata, enabling detection of correlated missingness patterns. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredColumns": {
   "type": "array",
   "maxItems": 14,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tabular-records-missingness-co-occurrence-counter-62e52fc8/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)