# Neural Interface Records - Missingness Co-occurrence Counter

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

Counts paired missing values (co-occurring null/absent owner, revision, and content pins) in neural-interface model/calibration/pipeline records without treating missing as matching.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/neural-interface-records/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020326/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/neural-interface-records-missingness-co-occurrence-counter-b9cc6db9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G2z-rcRZLfuJZb2ob7Mgw

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 neural-interface-records-missingness-co-occurrence-counter-b9cc6db9 -d '<json body>'
```

Example prompt: Check these 10 synthetic neural-interface calibration records for co-occurring missing values — I need a count of how many rows are simultaneously missing their owner pin, revision pin, or content pin without treating any missing value as a match.

## When to prefer this

Use this endpoint when you need to detect and count co-occurring (paired) missing values in neural-interface model, calibration, or pipeline records specifically, and you need guarantees that a missing value is never silently treated as a match. Prefer this over generic null-check tools when working with structured pin-based neural-interface records (owner, revision, content) and when auditability of missingness patterns matters.

## Known failure modes

- Empty or malformed rows array returns validation error
- dataClass value outside 'public' or 'synthetic' enum rejected
- nonpersonalMetadata not set to true (const) causes rejection
- More than 32 rows or fewer than 1 row returns schema validation error
- Missing required fields in individual row objects may produce partial counts
- Payment not supplied or insufficient USDC causes 402 error

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for synthetic neural-interface model/calibration/pipeline Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of paired/co-occurring missing values across owner, revision, and content pin fields for the supplied neural-interface record rows, clearly distinguishing absence from matching and identifying how often multiple pins are simultaneously null.

## 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/neural-interface-records-missingness-co-occurrence-counter-b9cc6db9/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)