# Alloy Measurements - Required Field Coverage

> Alloy Measurements - Required Field Coverage is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010137/call, status unknown (last checked 2026-10-25).

Checks which required fields (dataset, method, revision, content pins) are present or missing in supplied alloy measurement records

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/required-field-coverage?utm_source=zero.xyz
- Price: $0.010137/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-required-field-coverage-e5e76bbb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vvwvHgo3-XJWhLMq8rCaI

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-required-field-coverage-e5e76bbb -d '<json body>'
```

Example prompt: Check these 10 alloy lot measurement rows for missing required fields — I need coverage on dataset, method, revision, and content pins; the data class is synthetic and nonpersonal metadata is true.

## When to prefer this

Choose this endpoint when you need to programmatically audit alloy measurement records for missing required metadata fields (dataset, method, revision, content pins) before downstream analysis or storage. It is purpose-built for alloy lot/method/composition-basis data quality checks, not general-purpose schema validation or independent certification. Prefer it over generic validation tools when working specifically with scientific alloy measurement datasets classified as public or synthetic.

## Known failure modes

- rows array empty or exceeds 32 item limit — validation error
- requiredFields array missing or exceeds 8 items — request rejected
- nonpersonalMetadata not explicitly set to true — request rejected
- dataClass value not in enum ['public','synthetic'] — invalid input error
- Malformed row objects that don't match expected schema — partial or full failure
- Network or payment authorization failure — 402 or 5xx response

## How this service works

Check presence of required scientific dataset/method/revision/content pins; null is missing, not an invalid credential or artifact for alloy lot/method/composition-basis Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-row report indicating which required fields (e.g. dataset, method, revision, content pins) are present or null/missing in each supplied alloy measurement record, enabling identification of incomplete entries before further processing or certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/alloy-measurements-required-field-coverage-e5e76bbb/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)