# Tool Schemas Missingness Co-occurrence Analyzer

> Tool Schemas Missingness Co-occurrence Analyzer is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.020304/call, status unknown (last checked 2026-10-28).

Counts joint missing owner, input schema, and output schema pins across a batch of tool-schema declarations to quantify co-occurrence patterns of incomplete metadata fields.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020304/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-missingness-co-occurrence-analyzer-b541d9c6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CcFn8qYgwWao4Xj_RcjfZ

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 tool-schemas-missingness-co-occurrence-analyzer-b541d9c6 -d '<json body>'
```

Example prompt: Can you check these 5 tool schema contracts for joint missingness — specifically where owner, input schema, and output schema pins are all missing together? Treat this as public, nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need to statistically characterize the incompleteness of tool schema declarations at the metadata level — specifically to understand which fields (owner, input schema, output schema) tend to be missing together. It is appropriate for offline, nonpersonal, public or synthetic metadata only and is not a runtime availability or safety check. Prefer it over generic schema validators when the goal is co-occurrence analysis rather than simple field presence checks.

## Known failure modes

- Batch exceeds 32 contracts — returns validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Empty contracts array (minItems:1 not met) — schema validation error
- Malformed contract objects in array — parse or schema error
- Payment not provided or insufficient — 402 payment required

## How this service works

Count joint missing owner, input and output schema pins in tool-schema declaration metadata. An incomplete declaration does not establish an unavailable or unsafe runtime service. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts of joint missing field combinations across the submitted tool schema contracts — specifically how many contracts are simultaneously missing owner pins, input schema pins, and/or output schema pins, along with co-occurrence metrics for each combination of absent fields. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contracts": {
   "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/tool-schemas-missingness-co-occurrence-analyzer-b541d9c6/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)