# Incident Notes — Required-Field Coverage

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

Validates incident metadata records for missing required fields (service, start-time, and event-digest), reporting any gaps without processing raw logs, credentials, or sensitive data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/incident-notes/required-field-coverage?utm_source=zero.xyz
- Price: $0.010091/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/incident-notes-required-field-coverage-a64471b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FJ8tSUjGCtxZuPQaOVPXo

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 incident-notes-required-field-coverage-a64471b6 -d '<json body>'
```

Example prompt: Can you check these 5 incident metadata records — all public data, nothing personal — and tell me which ones are missing their service name, start time, or event-digest declaration?

## When to prefer this

Choose this endpoint when you need a lightweight, privacy-safe check of incident metadata completeness — specifically for required fields (service, start-time, event-digest) — without sending raw logs or sensitive operational data. Ideal for pre-ingestion validation pipelines, quality gates before archiving incident records, or compliance checks on synthetic or public incident datasets.

## Known failure modes

- Request includes personal data, causing rejection since only nonpersonal metadata is accepted
- nonpersonalMetadata flag is not set to true, causing validation failure
- incidents array is empty or exceeds 32 items, violating schema constraints
- dataClass is not one of 'public' or 'synthetic', causing enum rejection
- Raw logs or credentials included in payload, which are explicitly disallowed

## How this service works

Report missing service, start-time and event-digest declarations in nonpersonal incident metadata. No raw logs, credentials, incident diagnosis or proof of an outage. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A report identifying which incident metadata records are missing one or more required fields (service, start-time, event-digest), returned as structured coverage findings. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

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

## More

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