# Sky Observations - Missingness Co-occurrence

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

Counts paired missing values across owner, revision, and content pins in sky frame/epoch/observer/method-pinned observation records, without treating missing as matching.

## Facts

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

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 sky-observations-missingness-co-occurrence-ddcdbd48 -d '<json body>'
```

Example prompt: I have up to 32 sky observation records tagged as synthetic data — can you check how often the owner, revision, and content pins are missing together simultaneously, making sure a missing value is never counted as a match?

## When to prefer this

Use this endpoint when you need to audit co-occurring missingness specifically across owner, revision, and content pins in sky observation records pinned by frame, epoch, observer, and method — and when it is critical that absent values are never silently treated as matching values. Prefer this over generic null-count tools when the domain is celestial/astronomical observation data and you need pair-level co-occurrence statistics rather than per-field counts.

## Known failure modes

- rows array empty or exceeds 32-item limit — validation error returned
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- malformed row structure — parsing error
- network timeout for large row batches

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for sky frame/epoch/observer/method-pinned 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 pins within the supplied sky observation rows, broken down by pin combination, without conflating absence with a matching value. This is a supplied-record analysis, not 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/sky-observations-missingness-co-occurrence-ddcdbd48/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)