# Ephemeris Snapshots Missingness Co-occurrence

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

Counts paired missing owner, revision, and content pins in ephemeris snapshot records, detecting co-occurring null combinations without treating missing as matching.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020329/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ephemeris-snapshots-missingness-co-occurrence-da24a3cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dDUhtlIWvL9ODB0454nvx

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 ephemeris-snapshots-missingness-co-occurrence-da24a3cb -d '<json body>'
```

Example prompt: Can you check these 15 ephemeris snapshot rows (public data) and count how many have paired missing fields — like where owner and revision are both null at the same time, or target and centre are missing together?

## When to prefer this

Choose this endpoint when you need to audit supplied ephemeris snapshot records specifically for co-occurring missing metadata pins (owner, revision, content, target, centre, frame, time-scale, correction, kernel) and need accurate null detection that does not treat missing as matching. Best for pre-ingestion data quality checks, pipeline output validation, and multi-field missingness analysis on celestial ephemeris data — not for independent certification or recomputing ephemeris values.

## Known failure modes

- More than 32 rows submitted — input array exceeds maxItems limit
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true — const constraint violation
- Empty rows array (minItems 1 not met)
- Malformed row objects not matching expected ephemeris snapshot structure

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for target/centre/frame/time-scale/correction/kernel-pinned ephemeris Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of co-occurring missing pin combinations across owner, revision, content, target, centre, frame, time-scale, correction, and kernel fields in the supplied ephemeris snapshot rows — identifying how often each pair of fields is simultaneously null, without treating absent values as 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/ephemeris-snapshots-missingness-co-occurrence-da24a3cb/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)