# API Contracts - Condition Coverage Map

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

Compares caller-required HTTP contract review-check IDs against supplied check states to identify missing or unknown coverage entries

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/condition-coverage-map?utm_source=zero.xyz
- Price: $0.03509/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-condition-coverage-map-09017c61
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wkbvpGAK13FcNwaABG3Ga

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-condition-coverage-map-09017c61 -d '<json body>'
```

Example prompt: Check my HTTP contract condition coverage — I have required checks ['auth-check-01','schema-pin-02','rate-limit-03'] and my supplied states cover ['auth-check-01','schema-pin-02']; data class is synthetic and nonpersonal metadata is true. Tell me which required checks are missing or unrecognized.

## When to prefer this

Choose this endpoint when you need to programmatically identify which required HTTP contract check IDs are absent from or unrecognized in a supplied set of check states — especially useful in CI/CD pipelines, pre-deployment audits, or QA workflows where condition coverage completeness must be verified against a declared set of required checks. Prefer it over manual review when dealing with up to 32 check entries and when working exclusively with public or synthetic (non-personal) data.

## Known failure modes

- Empty or null requiredChecks array causes validation error (minItems:1 not met)
- Supplying more than 32 items in either checks or requiredChecks array triggers a maxItems constraint violation
- dataClass value outside 'public' or 'synthetic' enum causes rejection
- nonpersonalMetadata set to anything other than true (const:true) causes rejection
- Malformed input JSON or missing required fields returns a parsing/schema error
- Network or service unavailability returns a timeout or 5xx error

## How this service works

Compare caller-required HTTP contract 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 condition coverage map indicating which required check IDs are missing from the supplied states and which supplied states are unknown or unrecognized, helping callers identify gaps in their HTTP contract review process. Results are retained for 24 hours; minimal receipt metadata is retained 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/api-contracts-condition-coverage-map-09017c61/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)