# Reading Plans - Missingness Co-occurrence Analysis

> Reading Plans - Missingness Co-occurrence Analysis is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.02034/call, status unknown (last checked 2026-10-20).

Counts paired missing values across owner, revision, and content pins in reading plan records, detecting co-occurring missingness without conflating absent values with matching values.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.02034/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-missingness-co-occurrence-analysis-36960cff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1BeolMl5kehcw6baCsMS5

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 reading-plans-missingness-co-occurrence-analysis-36960cff -d '<json body>'
```

Example prompt: Can you run a missingness co-occurrence check on these 10 synthetic reading plan rows to see which combinations of owner, revision, and content pins are simultaneously absent — making sure we're not treating missing values as matches?

## When to prefer this

Choose this endpoint when you need to detect and count paired absences across owner, revision, and content pins in reading plan records specifically — particularly when you need to ensure missing values are not silently treated as matching values. Prefer this over generic data quality tools when working with library/plan/work/edition/revision-pinned records and needing co-occurrence missingness semantics rather than simple null counts.

## Known failure modes

- Exceeds 32-row limit — request rejected with validation error
- nonpersonalMetadata not set to true — request rejected
- Invalid dataClass value outside 'public' or 'synthetic' enum — rejected
- Empty rows array — rejected due to minItems:1 constraint
- Malformed row objects — partial or full analysis failure
- Service unavailable — HTTP 5xx with no analysis returned

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for library/plan/work/edition/revision-pinned reading 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 pins for the supplied reading plan rows, identifying which pin fields are simultaneously absent across records without treating missing values as matches.

## 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/reading-plans-missingness-co-occurrence-analysis-36960cff/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)