# Battery Measurements - Missingness Co-occurrence

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

Counts co-occurring missing values across owner, revision, and content pin fields in battery/cell-config/lot/method-pinned supplied records without silently treating missing as matching.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/battery-measurements/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020322/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/battery-measurements-missingness-co-occurrence-92aec0f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G46oQ78F5fly4KrdNGEp4

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 battery-measurements-missingness-co-occurrence-92aec0f2 -d '<json body>'
```

Example prompt: Check my batch of up to 32 synthetic battery cell-config records and count how often owner, revision, and content pins are simultaneously missing — make sure missing fields aren't being treated as matching values.

## When to prefer this

Use this endpoint when you need to explicitly count and surface co-occurring missing pin values in battery measurement or cell-config records and cannot allow silent null-as-match treatment. Prefer this over generic data validation tools when working specifically with battery/cell-config/lot/method pin-structured records and needing per-combination missingness counts rather than row-level pass/fail.

## Known failure modes

- rows array empty or exceeds 32 item limit — validation error returned
- dataClass value not in allowed enum (public, synthetic) — request rejected
- nonpersonalMetadata not set to true — request rejected
- malformed row objects missing expected pin fields — partial or error response
- network timeout on large row payloads

## How this service works

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

## Output

Returns counts of co-occurring missing values across pin fields (owner, revision, content, battery/cell-config/lot/method) in the supplied rows, distinguishing exact co-missing combinations without equating missing with matching values.

## 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/battery-measurements-missingness-co-occurrence-92aec0f2/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)