# Telescope Calibrations – Missing Co-occurrence Counter

> Telescope Calibrations – Missing Co-occurrence Counter is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.02033/call, status unknown (last checked 2026-10-16).

Counts paired missing values across owner, revision, and content pins for telescope calibration records (instrument/detector/filter/binning/readout/pipeline), flagging co-occurrences without treating nulls as matches

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/telescope-calibrations/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.02033/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/telescope-calibrations-missing-co-occurrence-counter-11860d10
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eCKC5t4HlJiPP273U44i2

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 telescope-calibrations-missing-co-occurrence-counter-11860d10 -d '<json body>'
```

Example prompt: Analyze these telescope calibration records and count how many have co-occurring missing owner, revision, and content pins — I'm only using public data and these are non-personal metadata records. I want to know which pin combinations (instrument, detector, filter, binning, readout, pipeline) are missing together, not just individually.

## When to prefer this

Use this endpoint when you need to count how often multiple calibration pin fields are simultaneously absent in telescope calibration records, specifically distinguishing true co-missing pairs from cases where a null is mistakenly treated as a matching value. Prefer this over generic null-checks when you need structured co-occurrence statistics across the full set of instrument/detector/filter/binning/readout/pipeline dimensions.

## Known failure modes

- Exceeds maxItems limit of 32 rows — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not explicitly set to true — rejected
- Malformed or empty rows array — schema validation error
- Missing required fields in individual row objects — analysis may return incomplete results

## How this service works

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

## Output

Returns counts of paired (co-occurring) missing values across calibration pin dimensions (owner, revision, content, instrument, detector, filter, binning, readout, pipeline), distinguishing each combination of simultaneously absent fields without treating a missing value as a match for a present one.

## 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/telescope-calibrations-missing-co-occurrence-counter-11860d10/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)