# Glossary Records Required Field Coverage Checker

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

Checks whether required fields (issuer/subject or producer/work pins) are present or null in supplied glossary record rows for vocabulary, term, language, namespace, or revision-pinned glossaries.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/glossary-records/required-field-coverage?utm_source=zero.xyz
- Price: $0.010181/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glossary-records-required-field-coverage-checker-358d8dec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QridHhPbwpL53qHW-Yqke

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 glossary-records-required-field-coverage-checker-358d8dec -d '<json body>'
```

Example prompt: Check these 5 glossary records for required field coverage — I need to know which rows are missing their issuer or subject pins; the data class is 'public' and nonpersonal metadata is true, required fields are ['issuer','subject'].

## When to prefer this

Choose this endpoint when you need to programmatically audit whether specific required metadata fields (such as issuer/subject or producer/work pins) are populated in glossary or vocabulary records before downstream processing, submission, or review. It is specifically suited for vocabulary/term/language/namespace/revision-pinned glossary data validation rather than general schema validation or independent credential certification.

## Known failure modes

- rows array exceeds 32 items — request rejected
- requiredFields array exceeds 8 items — request rejected
- nonpersonalMetadata not set to true — validation error
- dataClass value not in enum ['public','synthetic'] — invalid input
- empty rows array (minItems:1 violated) — bad request
- empty requiredFields array (minItems:1 violated) — bad request

## How this service works

Check presence of required issuer/subject or producer/work pins; null is missing, not an invalid credential or artifact for vocabulary/term/language/namespace/revision-pinned glossary Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-row analysis indicating which required fields are present and which are null or missing, allowing the caller to identify incomplete glossary records 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/glossary-records-required-field-coverage-checker-358d8dec/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)