# Meeting Records — Condition Coverage Map

> Meeting Records — Condition Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035042/call, status unknown (last checked 2026-10-15).

Compares role-level meeting review requirements against approved, rejected, or unknown declarations to produce a checklist coverage map.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/meeting-records/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035042/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meeting-records-condition-coverage-map-1e06564c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NoPsBklUj59k7eIi38mA-

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 meeting-records-condition-coverage-map-1e06564c -d '<json body>'
```

Example prompt: Can you run a condition coverage map on these 5 meeting review records against the required roles 'chair', 'secretary', and 'observer'? The data is synthetic and nonpersonal — I want to see which roles have approved, rejected, or unknown declarations.

## When to prefer this

Use this endpoint when you need a lightweight, metadata-only checklist audit of meeting review declarations against role requirements — specifically when all data is nonpersonal (public or synthetic) and you want a fast coverage comparison without triggering identity verification or consent workflows. Prefer this over heavier compliance platforms when you only need a declarative gap map, not verified authorization or participant identity.

## Known failure modes

- Empty or malformed reviews array may return incomplete coverage map
- requiredRoles array exceeds 4 items — request rejected
- dataClass must be 'public' or 'synthetic'; other values cause validation error
- nonpersonalMetadata must be explicitly true; omission or false value will fail
- reviews array exceeding 32 items will be rejected
- Service unavailable or timeout if the API endpoint is temporarily down

## How this service works

Compare role-level meeting review requirements with approved/rejected/unknown declarations. This is checklist metadata, not verified participant identity, consent or authorization. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured coverage map showing, for each required role, whether the meeting review declarations are approved, rejected, or unknown — along with aggregate coverage statistics. Results are valid for 24 hours; minimal receipt metadata is retained for 90 days. No verified participant identity or consent data is included.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meeting-records-condition-coverage-map-1e06564c/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)