# Publication Records Missingness Co-occurrence Checker

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

Counts paired missing owner, revision, and content pins in publication record rows without treating absent values as matches, for bibliographic supplied-record analysis.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020332/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-missingness-co-occurrence-checker-4c4cafc3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qNOGQ3eGLItAXuVDzDCwk

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 publication-records-missingness-co-occurrence-checker-4c4cafc3 -d '<json body>'
```

Example prompt: Can you check this batch of up to 32 publication records — marked as public data and nonpersonal metadata — and count how many have co-occurring missing owner, revision, or content pins, making sure a blank value isn't silently treated as a match?

## When to prefer this

Choose this endpoint when you need to detect co-occurring missing pins in publication records without risking false matches from absent values, especially for bibliographic audits involving owner, revision, content, DOI, publisher, work, or edition pins. Prefer over generic data-quality tools when the domain is scholarly or bibliographic metadata and you need paired-missingness semantics rather than simple null counts.

## Known failure modes

- More than 32 rows submitted — API rejects with validation error
- nonpersonalMetadata not set to true — request rejected as const violation
- Invalid dataClass value outside 'public' or 'synthetic' enum — schema validation failure
- Empty rows array — rejected due to minItems:1 constraint
- Malformed row objects — processing error or partial results
- Payment failure via x402 — endpoint returns 402 before processing

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for publisher/work/DOI/edition-pinned bibliographic Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of paired missing pin co-occurrences across owner, revision, and content fields for each supplied publication record row, without silently treating missing values as matches — enabling targeted remediation of bibliographic data gaps.

## 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/publication-records-missingness-co-occurrence-checker-4c4cafc3/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)