# Trial Registry Records - Schema Directionality Analysis

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

Compares closed export-field directionality in supplied trial registry records, reporting schema-level field analysis without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/trial-registry-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035271/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-schema-directionality-analysis-833986ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yHhjZQzm4Zl1WU2Kd5D_c

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-schema-directionality-analysis-833986ad -d '<json body>'
```

Example prompt: Compare the schema directionality of these two trial registry record snapshots — the before set has up to 10 records and the after set has 8 records, both using public data class, with nonpersonalMetadata set to true, and the consumer does allow extra fields.

## When to prefer this

Choose this endpoint when you need to audit schema-level directionality changes in trial registry record exports between two states (before/after), particularly for closed export fields in public or synthetic datasets. It is not a raw data parser, CSV reader, or independent certifier — prefer it specifically for structural schema comparison tasks on trial registry data where nonpersonal metadata handling is required.

## Known failure modes

- before array empty or exceeds 32 items — validation error
- after array exceeds 32 items — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation error
- nonpersonalMetadata not set to true (const constraint) — rejected
- malformed record objects in before or after arrays — parse error
- network timeout for large record sets — retry recommended

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a schema-level directionality comparison of closed export fields between the before and after record arrays, identifying directional shifts, field presence changes, and schema consistency signals. Does not include raw data cells or independent certification — analysis is based solely on the supplied records.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trial-registry-records-schema-directionality-analysis-833986ad/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)