# License Records - Missingness Co-occurrence Counter

> License Records - Missingness Co-occurrence Counter is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.020308/call, status unknown (last checked 2026-11-04).

Counts paired co-occurring missing fields (owner, revision, content pins) in nonpersonal license and permission-manifest metadata without treating absent values as matches.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/license-records/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020308/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/license-records-missingness-co-occurrence-counter-c6989014
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fyiJy3jEv-2P_7o4Ukoeu

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 license-records-missingness-co-occurrence-counter-c6989014 -d '<json body>'
```

Example prompt: Check these 20 public license metadata rows for co-occurring missing fields — specifically where owner, revision, and content pin are jointly absent — and give me a count of each paired missingness pattern. The data is nonpersonal and public-class.

## When to prefer this

Use this endpoint when you need to specifically count paired co-occurring field absences in nonpersonal license or permission-manifest metadata (public or synthetic data only, up to 32 rows) and require strict absent-is-not-matching semantics. Prefer it over general data-quality tools when your focus is joint missingness patterns in license/rights metadata rather than single-field presence checks, duplicate detection, or live rights clearance.

## Known failure modes

- Rows array empty or exceeds 32-item maximum — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true (const) — request rejected
- Rows contain personal data — outside declared scope, caller responsibility
- Malformed row objects without expected metadata fields — undefined behavior or empty counts
- Network or payment failure — no result returned, transaction may not complete

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for nonpersonal work and permission-manifest metadata. No authoritative license interpretation, rights clearance, agreement acceptance, royalty transfer or legal advice. Satisfied conditions are caller declarations only. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A count of co-occurring (jointly absent) pairs among the owner, revision, and content-pin metadata fields across the submitted rows, distinguishing each combination of paired absence without treating missing values as matching values. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## 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/license-records-missingness-co-occurrence-counter-c6989014/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)