# Api Contracts — Required-field Coverage

> Api Contracts — Required-field Coverage is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010103/call, status unknown (last checked 2026-10-19).

Checks HTTP contract metadata for absent owner, route/method, or schema pin declarations and reports missing required fields.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/required-field-coverage?utm_source=zero.xyz
- Price: $0.010103/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-required-field-coverage-2eb6d522
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A-0RB8VB6h9CoIdF3zFXj

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 api-contracts-required-field-coverage-2eb6d522 -d '<json body>'
```

Example prompt: Check these 5 API contracts for missing required fields — I want to know which ones are missing owner, route/method, or schema pin declarations. All the data is public and non-personal.

## When to prefer this

Choose this endpoint when you need an offline, deterministic check for missing required fields (owner, route/method, schema pin) in HTTP contract metadata, without any remote schema fetching or payability verification. Ideal for CI pipelines, pre-registration audits, or governance workflows where you have up to 32 contract records and need a fast, structured missing-field report on non-personal metadata only.

## Known failure modes

- Input array is empty or exceeds 32 items — request rejected
- nonpersonalMetadata is not set to true — request rejected
- dataClass value is not 'public' or 'synthetic' — validation error
- Malformed contract objects in the input array — parsing error
- Service unavailable — HTTP 5xx response

## How this service works

Report absent owner, route/method or schema pin declarations in supplied HTTP-contract metadata. No remote schema fetch or assurance that the route is payable or executable. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A report identifying which of the supplied HTTP contract metadata entries are missing required declarations, specifically: absent owner fields, missing route or HTTP method specifications, and absent schema pin declarations. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No remote schema fetching is performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contracts": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-contracts-required-field-coverage-2eb6d522/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)