# Payment Quotes - Condition Coverage Map

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

Compares required quote-review check IDs against declared satisfied, unsatisfied, or unknown condition states to identify coverage gaps in payment quote metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/payment-quotes/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035072/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-quotes-condition-coverage-map-fa04bc39
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FEyAYEy6CCA12Dv0u7gGX

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 payment-quotes-condition-coverage-map-fa04bc39 -d '<json body>'
```

Example prompt: Can you check the condition coverage for my payment quote review — I have required checks ['chk-001','chk-002','chk-003'] and my declared checks are ['chk-001','chk-002'] with 'chk-003' unknown, using public data class? I want to see which conditions are satisfied, unsatisfied, or unknown.

## When to prefer this

Choose this endpoint when you need to audit or validate which required payment quote review conditions have been declared satisfied, unsatisfied, or unknown — particularly in workflows that need to confirm coverage completeness before advancing a quote. It is purely a metadata comparison tool with no live payment execution, making it safe for pre-flight checks and compliance audits on nonpersonal quote metadata.

## Known failure modes

- Empty or missing requiredChecks array (minItems:1 violated) causes validation error
- checks array exceeds 32 items causes rejection
- nonpersonalMetadata not set to true (const:true) causes schema rejection
- dataClass value outside 'public' or 'synthetic' enum causes error
- Malformed check IDs or non-array types cause input validation failure

## How this service works

Compare required quote-review check IDs with declared satisfied, unsatisfied or unknown states. No evidence of facilitator acceptance, actual payment or result delivery. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a condition coverage map showing which required check IDs are satisfied, unsatisfied, or in unknown states, along with any uncovered or missing checks — retained for 24 hours, with minimal receipt metadata kept for 90 days. No live payment processing or actual result delivery occurs.

## 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/payment-quotes-condition-coverage-map-fa04bc39/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)