# Market Catalogues - Condition Coverage Map

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

Validates that every requested module name has exactly one caller-declared present module entry within a specified catalogue record, organization, jurisdiction, source, and revision.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/market-catalogues/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035294/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/market-catalogues-condition-coverage-map-169b7029
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ifmm6eV0Wv6iij3xMTSkc

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 market-catalogues-condition-coverage-map-169b7029 -d '<json body>'
```

Example prompt: Check the condition coverage map for catalogue ref 'CAT-2024-Q3', SKU 'SKU-88721', scope 'US-WEST', revision 'v4', using public data class — I need to verify that the modules ['pricing','availability','compliance'] are all present with exactly one record each.

## When to prefer this

Use this endpoint when you need to confirm that a market catalogue record contains exactly one declared-present module entry per requested module name, scoped to a specific catalogue reference, revision, SKU, and jurisdiction. Prefer this over generic schema validators when the business rule is strict one-to-one module presence within a catalogue record hierarchy, and when the data is already caller-supplied (this endpoint performs supplied-record analysis, not independent data certification).

## Known failure modes

- Module with zero matching records — coverage gap returned for that module
- Module with more than one matching record — ambiguous coverage error
- Invalid or unrecognized catalogue reference — request rejected
- requiredModules array empty or exceeds 4-item limit — schema validation error
- rows array exceeds 32-item limit — schema validation error
- nonpersonalMetadata not set to true — request rejected
- Unrecognized dataClass value — enum validation error

## How this service works

Require exactly one caller-declared present module per requested module name in an identical organization/record/jurisdiction/source/revision Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured coverage map indicating, for each requested module name, whether exactly one caller-declared present record exists within the specified catalogue, organization/scope, revision, and source. Returns pass/fail status per module and highlights any modules with zero or multiple matching records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "skuRef": {
   "type": "string"
  },
  "scopeRef": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "merchantRef": {
   "type": "string"
  },
  "catalogueRef": {
   "type": "string"
  },
  "productDigest": {
   "type": "string"
  },
  "requiredModules": {
   "type": "array",
   "maxItems": 4,
   "minItems": 1
  },
  "catalogueRevision": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/market-catalogues-condition-coverage-map-169b7029/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)