# Spectrometry Records Missingness Co-occurrence

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

Counts co-occurring missing values across owner, revision, and content pins in spectrometry records without treating missing as matching

## Facts

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

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 spectrometry-records-missingness-co-occurrence-d930c0fd -d '<json body>'
```

Example prompt: Analyze these spectrometry records (up to 32 rows, public data, non-personal metadata only) and count how often owner, revision, and content pins are simultaneously missing — don't treat a missing value as a match.

## When to prefer this

Choose this endpoint when you need to count paired or simultaneous missingness across multiple pin fields (owner, revision, content) in spectrometry records and must ensure that missing values are never silently treated as matching values. Prefer it over generic data-quality tools when working specifically with instrument/calibration/method-pinned spectral data in small batches (up to 32 rows).

## Known failure modes

- Rows array exceeds 32 items — request rejected
- nonpersonalMetadata not set to true — validation error
- Invalid dataClass value outside 'public' or 'synthetic' enum — bad request
- Empty rows array — minimum 1 item required
- Malformed row structure — schema validation failure

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for instrument/calibration/method-pinned spectrum Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of co-occurring missing values across owner, revision, and content pins in the supplied spectrometry rows, distinguishing absent values from matches without silently equating nulls — based purely on the supplied records, not an independent certification.

## 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/spectrometry-records-missingness-co-occurrence-d930c0fd/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)