# Alloy Measurements Missingness Co-occurrence

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

Counts paired missing values across owner, revision, and content pins in alloy lot/method/composition-basis records without treating missing as matching.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.02032/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-missingness-co-occurrence-11efb668
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H-J44s3SvDV9IF3IcaQqQ

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 alloy-measurements-missingness-co-occurrence-11efb668 -d '<json body>'
```

Example prompt: Check this batch of up to 32 alloy measurement rows (public data, nonpersonal metadata only) for co-occurring missing values across owner, revision, and content pins — I need counts of how often those fields are simultaneously absent without any missing value being silently treated as a match.

## When to prefer this

Choose this endpoint when you need to explicitly count co-occurring missing owner, revision, and content pins in alloy lot, method, or composition-basis measurement records and require a guarantee that missing values are never silently treated as matching values — particularly important for pre-submission data audits or compliance checks on supplied (not independently certified) alloy records.

## Known failure modes

- More than 32 rows supplied — request rejected with validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true — const validation failure
- Empty rows array — minItems violation
- Malformed row objects — schema validation error
- Network or payment authorization failure via x402 protocol

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for alloy lot/method/composition-basis Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of paired missing values across owner, revision, and content pin fields for the supplied alloy measurement rows, clearly distinguishing absence from implicit matching so that missing values are never silently treated as equivalent.

## 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/alloy-measurements-missingness-co-occurrence-11efb668/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)