# Publication Records - Required Field Coverage

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

Checks whether specified required fields are present across supplied bibliographic publication records, flagging null/missing values without treating them as invalid credentials or artifacts.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/required-field-coverage?utm_source=zero.xyz
- Price: $0.010161/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-required-field-coverage-2f7e55fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l8Q06NIVIWsh3vC8RIY5E

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 publication-records-required-field-coverage-2f7e55fe -d '<json body>'
```

Example prompt: Check these 10 public publication records to see if all of the required fields — DOI, author, revision, and content pin — are present; flag any rows where those fields are null.

## When to prefer this

Choose this endpoint when you need to quickly audit a batch of up to 32 bibliographic or scientific publication records for the presence of caller-specified required fields, particularly when you want null-detection (not credential or artifact validation). Prefer this over generic schema validators when the context is specifically bibliographic/DOI-pinned records and you need per-field, per-row coverage results.

## Known failure modes

- Rows array is empty or exceeds 32 items — request rejected
- requiredFields list is empty or exceeds 8 entries — request rejected
- nonpersonalMetadata is not set to true — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation error
- Malformed row structure causes parsing failure
- Network timeout on large row payloads

## How this service works

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

## Output

Returns a per-record analysis indicating which required fields are null or missing across the supplied rows, without independently certifying credentials or artifact validity. Null values are flagged as missing rather than as invalid.

## 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/publication-records-required-field-coverage-2f7e55fe/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)