# Provenance Manifests Required-Field Coverage Check

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

Checks caller-supplied provenance manifest rows for the presence of required issuer/subject or producer/work pins, returning null for missing fields without downloading sources or verifying signatures.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/provenance-manifests/required-field-coverage?utm_source=zero.xyz
- Price: $0.010111/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/provenance-manifests-required-field-coverage-check-82d078e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_evz2GdeRUgfEmNIegkzi3

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 provenance-manifests-required-field-coverage-check-82d078e6 -d '<json body>'
```

Example prompt: Check these 10 provenance manifest rows for required-field coverage — specifically make sure the issuer and subject pins are all present, treat the data as public and nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need a lightweight, offline check that required provenance metadata pins (issuer, subject, producer, work) are present in manifest rows — without any source download, signature verification, or proof-of-origin logic. Prefer this over heavier provenance pipelines when you only need field-presence coverage for public or synthetic nonpersonal metadata at low cost per call.

## Known failure modes

- Rows array empty or exceeds 32-item limit — validation error
- requiredFields array empty or exceeds 8-item limit — validation error
- nonpersonalMetadata not explicitly set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation error
- Malformed manifest row structure — fields may be reported as indeterminate
- Result expired after 24-hour retention window — no historical retrieval available

## How this service works

Check presence of required issuer/subject or producer/work pins; null is missing, not an invalid credential or artifact for caller-supplied artifact and dataset provenance manifests. No source download, build reproduction, signature verification, proof of origin, causality or scientific validity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a per-row coverage result indicating which required pins (issuer, subject, producer, work) are present or null/missing, without downloading source files, verifying signatures, or assessing scientific validity. Full results are retained for 24 hours; minimal receipt metadata for 90 days.

## 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/provenance-manifests-required-field-coverage-check-82d078e6/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)