# Bibliographies Condition Coverage Map

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

Validates that each requested bibliography module has exactly one caller-declared present entry within the same organization/record/jurisdiction/source/revision scope.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/bibliographies/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035306/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bibliographies-condition-coverage-map-8f78a49f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nKpmp4xJaFB-5i6CQ-Cc1

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 bibliographies-condition-coverage-map-8f78a49f -d '<json body>'
```

Example prompt: Check the bibliography condition coverage for work reference 'WRK-2024-001' with scope 'legal-corpus', corpus reference 'CORP-7', revision 'v3', and required modules ['intro','methods','results'] using public data — I need to confirm exactly one entry per module is declared present.

## When to prefer this

Use this endpoint when you need to confirm that a bibliography dataset has exactly one declared-present entry per required module within a tightly scoped record context (same revision, corpus, and jurisdiction). It is a supply-record analysis tool, not an independent certification service — prefer it over general citation checkers when your workflow requires scoped, module-level condition coverage mapping tied to a specific bibliographyRevision and corpusRef.

## Known failure modes

- Missing required modules array — returns validation error
- More than 4 required modules submitted — rejected by schema
- Rows array exceeds 32 items — request rejected
- No matching entry found for a required module — coverage failure returned
- Multiple entries found for a single module — duplicate conflict reported
- Invalid dataClass value — enum constraint violation
- workRef or scopeRef not recognized — scope mismatch 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

Returns a condition coverage map indicating whether each requested module has exactly one caller-declared present entry within the matched organization/record/jurisdiction/source/revision scope, along with pass/fail status per module and any missing or conflicting entries.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "workRef": {
   "type": "string"
  },
  "scopeRef": {
   "type": "string"
  },
  "styleRef": {
   "type": "string"
  },
  "corpusRef": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "entryDigest": {
   "type": "string"
  },
  "requiredModules": {
   "type": "array",
   "maxItems": 4,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "bibliographyRevision": {
   "type": "string"
  }
 }
}
```

## More

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