# Technical Manuals Missingness Co-occurrence Counter

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

Counts joint absence (co-occurrence of missing values) across procedure unit, tolerance, and source-page metadata fields in technical manual datasets.

## Facts

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

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 technical-manuals-missingness-co-occurrence-counter-dec3179f -d '<json body>'
```

Example prompt: Check my public technical manual dataset for joint missingness across procedure unit, tolerance, and source-page metadata — I want to see how often those fields are absent together, using these parameters: ['procedure_unit', 'tolerance', 'source_page'].

## When to prefer this

Choose this endpoint when you need to quantify simultaneous absence of procedure unit, tolerance, and source-page metadata in technical manual datasets without any imputation or validity scoring. It is purpose-built for offline, typed, nonpersonal metadata analysis of public or synthetic data classes. Prefer it over general data profiling tools when you specifically need joint missingness counts (co-occurrence of missing fields) rather than per-field missingness rates or filled-value distributions.

## Known failure modes

- Invalid or missing dataClass enum value (must be 'public' or 'synthetic')
- parameters array outside allowed range (1–32 items)
- nonpersonalMetadata not set to true (required constant)
- Request contains personal data, which is not supported
- Malformed parameter entries causing parse failure
- Timeout or service unavailability returning 5xx errors

## How this service works

Count joint absence of procedure unit, tolerance and source-page metadata. Zero tolerance and page zero are supplied values; no imputation or engineering validity score. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts of joint absence (co-occurrence) for combinations of procedure unit, tolerance, and source-page metadata fields across the supplied parameter list. Results reflect raw observed missingness with no imputation, engineering validity scoring, or derived estimates. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "parameters": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/technical-manuals-missingness-co-occurrence-counter-dec3179f/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)