# Source Packs Missingness Co-occurrence

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

Counts joint absences of source digest, observation time, and byte-count declarations across a batch of source metadata records, without imputing or judging completeness.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/source-packs/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020298/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/source-packs-missingness-co-occurrence-c0bbe555
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ozX21YDi2fosNduwsA0Rs

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 source-packs-missingness-co-occurrence-c0bbe555 -d '<json body>'
```

Example prompt: Can you count the joint absences of source digest, observation time, and byte-count across these 12 public source pack records? I need to see which combinations of those fields are simultaneously missing — nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need to understand which source-level metadata fields are jointly absent in a batch of source pack records, specifically the triad of digest, observation time, and byte-count. It is ideal for offline, nonpersonal, typed metadata audits where you want co-occurrence statistics without any imputation, repair, or completeness judgment. Prefer it over generic data quality tools when your use case is specifically about correlated missingness patterns in source provenance metadata rather than value-level validation or schema enforcement.

## Known failure modes

- Empty or malformed sources array returns a validation error
- Providing more than 32 source records exceeds the maxItems limit and is rejected
- Omitting or setting nonpersonalMetadata to false fails schema validation (must be true)
- Supplying a dataClass value outside 'public' or 'synthetic' causes a schema rejection
- Network timeout if the batch is at the upper limit and server load is high
- 402 Payment Required if USDC payment is not properly attached via x402 protocol

## How this service works

Count joint absence of source digest, observation time and byte-count declarations. Zero-byte sources stay supplied; no imputation or completeness verdict. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts of joint absences across the three source declaration fields (digest, observation time, byte-count) for each co-occurrence combination present in the submitted source pack records. Zero-byte sources are included as supplied. No imputation, completeness verdicts, or joined cell data is returned. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sources": {
   "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/source-packs-missingness-co-occurrence-c0bbe555/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)