# Trial Registry Records - Source Coverage Map

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

Binds clinical trial registry record references to an exact owner/subject/revision/content/source frame for supply-level provenance analysis

## Facts

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

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-source-coverage-map-cb7202f6 -d '<json body>'
```

Example prompt: Map these 10 trial registry record rows to their source coverage frame — data class is 'public', nonpersonal metadata only — and tell me which sources each row is bound to by owner, subject, and revision.

## When to prefer this

Choose this endpoint when you need to bind a batch of trial registry record references to a precise provenance frame (owner, subject, revision, content, source) for supply-level analysis or audit handoff. It is best suited for public or synthetic data class scenarios involving nonpersonal metadata, where the goal is declared source coverage mapping rather than independent certification of underlying registry bytes.

## Known failure modes

- Missing or empty rows array returns validation error
- Source array exceeds maxItems of 32 causing rejection
- dataClass value outside 'public' or 'synthetic' enum fails schema validation
- nonpersonalMetadata not set to true (const) causes request rejection
- Unverified or malformed hash strings may produce incomplete frame bindings
- Empty or malformed source references result in partial coverage maps

## How this service works

Bind record references to an exact owner/subject/revision/content/source frame; hash-shaped strings are declarations, not independently verified source bytes for study-level registry/protocol/snapshot Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a source coverage map binding each supplied trial registry record row to an exact owner/subject/revision/content/source frame; hash-shaped strings represent caller-supplied declarations rather than independently verified source bytes, scoped to study-level registry and protocol snapshot analysis.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "sources": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

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