# Edition Records - Required Field Coverage

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

Checks whether required issuer/subject or producer/work pins are present in edition record rows, flagging nulls as missing fields rather than invalid credentials.

## Facts

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

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 edition-records-required-field-coverage-95fa2ee1 -d '<json body>'
```

Example prompt: Can you check whether the required fields — issuer and subject — are present in these edition records? I have up to 20 rows of public edition data and need to know which ones have null pins so I can flag them as missing.

## When to prefer this

Use this endpoint when you need to audit edition records (publisher, work, edition, format, or revision-pinned) for required field presence without requiring independent certification of the data. It is specifically designed for supplied-record analysis of edition-domain metadata and treats null as missing rather than invalid, making it suitable for pre-publication data quality checks.

## Known failure modes

- Rows array empty or exceeds 32-item limit — returns validation error
- requiredFields array empty or exceeds 8-item limit — returns validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Malformed row objects with unexpected structure — may return incomplete coverage results

## How this service works

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

## Output

Returns a per-row analysis indicating whether each required field (e.g. issuer, subject, producer, work) is present or null across the supplied edition records, distinguishing missing values from invalid credentials without independently certifying the data.

## 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/edition-records-required-field-coverage-95fa2ee1/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)