# Tool Schemas — Condition Coverage Map

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

Compares caller-required tool-schema declaration review-check IDs against supplied states to identify missing or unknown condition coverage gaps.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035096/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-condition-coverage-map-4d9da214
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lEg1U6HN0yDS3HPHx_dQO

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 tool-schemas-condition-coverage-map-4d9da214 -d '<json body>'
```

Example prompt: Can you run a condition coverage map for my tool-schema review? I have these required check IDs and want to see which ones are missing or have unknown states — the data is synthetic and nonpersonal.

## When to prefer this

Use this endpoint when you need a lightweight, offline comparison of tool-schema review-check IDs against a set of supplied states — specifically to find coverage gaps (missing or unknown states). Choose it over general compliance or approval endpoints because it explicitly does not produce approval, policy, security, or deployment verdicts; it is purely a coverage-mapping operation on typed, nonpersonal metadata.

## Known failure modes

- Empty requiredChecks array (minItems:1 violated) causes validation error
- More than 32 items in checks or requiredChecks arrays exceeds maxItems limit
- dataClass value outside allowed enum ('public' or 'synthetic') is rejected
- nonpersonalMetadata not set to true (const) causes schema rejection
- Malformed or non-array checks/requiredChecks fields cause 400-level errors

## How this service works

Compare caller-required tool-schema declaration review-check IDs with supplied states. Missing or unknown states are not approval, policy compliance, security verification or deployment readiness. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a coverage map showing which required check IDs have been matched to supplied states, which are missing entirely, and which supplied states are unrecognized or unknown — without any approval, policy compliance, security verification, or deployment readiness judgment. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tool-schemas-condition-coverage-map-4d9da214/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)