# Procurement Notices - Required Field Coverage Check

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

Checks whether required fields (issuer/subject or producer/work pins) are present in supplied procurement notice records, returning null for missing fields without validating credential authenticity.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/procurement-notices/required-field-coverage?utm_source=zero.xyz
- Price: $0.010167/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/procurement-notices-required-field-coverage-check-57add73a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-rLbRD78fHJvof_CcKzjZ

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 procurement-notices-required-field-coverage-check-57add73a -d '<json body>'
```

Example prompt: Can you check these 10 procurement notice records to see if the required fields — issuer, subject, and jurisdiction — are all present? The data is public, and I need to know which rows are missing any of those pins.

## When to prefer this

Use this endpoint when you have a batch of procurement notice records and need to verify that specific required fields (issuer, subject, producer, work, jurisdiction, kind, revision pins) are populated before downstream processing, compliance review, or ingestion. It is a lightweight structural presence check — not a credential validator or registry lookup — so prefer it for fast, cost-effective field coverage audits on up to 32 rows at a time.

## Known failure modes

- rows array empty or exceeds 32-item limit returns validation error
- requiredFields array exceeds 8 items or is empty triggers schema rejection
- dataClass not set to 'public' or 'synthetic' causes enum validation failure
- nonpersonalMetadata not set to true (const constraint) causes request rejection
- malformed row objects with unexpected types may cause field resolution errors

## How this service works

Check presence of required issuer/subject or producer/work pins; null is missing, not an invalid credential or artifact for buyer/notice/kind/jurisdiction/revision-pinned procurement 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 or null (missing), covering issuer/subject or producer/work pins and other declared required fields. Results reflect supplied-record analysis only — not independent certification of credential or artifact validity.

## 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/procurement-notices-required-field-coverage-check-57add73a/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)