# Planetary Measurements - Missingness Co-occurrence

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

Counts co-occurring missing values across owner, revision, and content pins in caller-supplied planetary measurement records without treating null as a match.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/planetary-measurements/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020331/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/planetary-measurements-missingness-co-occurrence-1d15ef3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X5vKs5Mh2kKx9OQ4P21tW

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 planetary-measurements-missingness-co-occurrence-1d15ef3a -d '<json body>'
```

Example prompt: Can you check these planetary measurement records — up to 32 rows of public data — and count how many have paired missing values across owner, revision, and content pins at the same time, without treating any blank as a match?

## When to prefer this

Use this endpoint when you need to detect joint absence patterns across multiple metadata pins in planetary measurement records specifically — not for single-field null checks, not for independent data certification, and not for non-planetary datasets. Best when you have structured rows of celestial records and need to understand which pin fields tend to be missing together.

## Known failure modes

- rows array exceeds 32 items returns validation error
- nonpersonalMetadata not set to true returns rejection
- dataClass not one of 'public' or 'synthetic' causes schema error
- empty rows array (minItems:1 violated) returns error
- malformed row objects may cause computation to fail or return partial results

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for target/site/convention/time/method-pinned planetary 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 pin fields in the supplied planetary measurement rows, distinguishing each paired absence combination without conflating missing with a matching value.

## 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/planetary-measurements-missingness-co-occurrence-1d15ef3a/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)