# Trial Registry Records - Condition Coverage Map

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

Checks declared present sections per caller-requested registry module against a supplied clinical trial registry record snapshot, returning a condition coverage map without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/trial-registry-records/condition-coverage-map?utm_source=zero.xyz
- Price: $0.03527/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trial-registry-records-condition-coverage-map-54890c31
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A0hM2IesAm8ktWU0uINPz

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 trial-registry-records-condition-coverage-map-54890c31 -d '<json body>'
```

Example prompt: Check the condition coverage map for study NCT00123456 using registry ClinicalTrials.gov, protocol digest abc123, snapshot digest def456, and verify that sections 'eligibility', 'outcomes', and 'interventions' are present — use public data class.

## When to prefer this

Choose this endpoint when you need to programmatically verify which declared sections are present in a specific clinical trial registry snapshot, given exact digest references and a list of required sections. It is best suited for compliance checking, audit workflows, or protocol completeness analysis where you hold the registry record references and need a structured coverage map rather than a full document retrieval.

## Known failure modes

- Invalid or unrecognized studyRef returns error or empty coverage map
- requiredSections array outside 1-5 items range causes validation failure
- rows array exceeding 32 items rejected
- Missing required fields such as registryRef or protocolDigest results in schema validation error
- Non-matching snapshotDigest or protocolDigest may return no coverage results
- dataClass value outside enum ['public','synthetic'] causes request rejection

## How this service works

Check one declared present section per caller-requested registry module in an identical registry/study/protocol/snapshot Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a condition coverage map indicating which of the caller-requested registry module sections are declared present within the supplied study/protocol/snapshot record. Results reflect supplied-record analysis only, not independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "studyRef": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "registryRef": {
   "type": "string"
  },
  "protocolDigest": {
   "type": "string"
  },
  "snapshotDigest": {
   "type": "string"
  },
  "requiredSections": {
   "type": "array",
   "maxItems": 5,
   "minItems": 1
  },
  "snapshotRevision": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trial-registry-records-condition-coverage-map-54890c31/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)