# Spectrometry Records - Required Field Coverage

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

Checks which required fields are present or missing in caller-supplied spectrometry dataset records, returning null for absent fields without treating absence as a credential or artifact error.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/spectrometry-records/required-field-coverage?utm_source=zero.xyz
- Price: $0.010131/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spectrometry-records-required-field-coverage-a4c8ca18
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E7ITVLQjMdt4ixsUiVMjl

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

Example prompt: Check my spectrometry records for required field coverage — I have up to 10 rows of public synthetic spectrum data and I need to know which of these required fields are missing: instrument_id, method_revision, calibration_pin, and content_hash. Nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need to audit caller-supplied spectrometry records for required field presence without independent certification. It is specifically suited for scientific spectrum, calibration, or method-pinned datasets where you want to detect null/missing fields across up to 32 rows against a custom required-field list, and only for public or synthetic, nonpersonal data.

## Known failure modes

- rows array empty or exceeds 32-item limit — validation error returned
- requiredFields array empty or exceeds 8-item limit — rejected
- dataClass not one of 'public' or 'synthetic' — enum validation error
- nonpersonalMetadata not explicitly true — request rejected
- Malformed row objects — field coverage check may yield incomplete results
- Network or payment authorization failure — HTTP 402 or 5xx returned

## How this service works

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

## Output

Returns a per-row or aggregate coverage report indicating which required fields are present (non-null) and which are missing (null) across the supplied spectrometry record rows, without making independent certification judgments about credential validity or artifact integrity.

## 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/spectrometry-records-required-field-coverage-a4c8ca18/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)