# Trial Registry Records - Scope Boundary Audit

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

Validates that clinical trial registry records conform to exact declared owner, subject, revision, and allowed scope labels, flagging any scope violations without granting permission or access.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/trial-registry-records/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038333/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-scope-boundary-audit-c4a3aa60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k4MuTHDtxDKmzhA-0f4qJ

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-scope-boundary-audit-c4a3aa60 -d '<json body>'
```

Example prompt: Audit these 5 trial registry record rows for scope boundary compliance — the owner is 'org-123', subject is 'trial-456', revision is 'v2', data class is 'public', and the allowed scopes are ['read', 'review']; nonpersonal metadata is true.

## When to prefer this

Use this endpoint when you need strict scope boundary enforcement on clinical trial registry or protocol records and require exact pin matching on owner, subject, revision, and scope labels. Prefer this over generic data validation endpoints when dealing specifically with study-level registry snapshots or trial protocol records that must conform to declared scope constraints without independent certification. Best suited for pre-submission compliance checks and audit trails in regulated research contexts.

## Known failure modes

- Missing required fields (ownerRef, subjectRef, revision, allowedScopes) returns a validation error
- Rows array exceeds maxItems (32) or is empty returns a schema error
- dataClass value outside 'public' or 'synthetic' enum returns a rejection
- nonpersonal metadata flag not set to true (const) causes request failure
- Mismatched revision strings produce scope violation flags rather than errors
- Network timeout on large row batches

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for study-level registry/protocol/snapshot Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit result indicating whether each supplied registry record row conforms to the exact declared owner, subject, revision, and allowed scope labels. Flags any records with scope boundary violations, pin mismatches, or unauthorized label usage. Does not grant access or certify records independently.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trial-registry-records-scope-boundary-audit-c4a3aa60/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)