# Trial Registry Records - Unit Label Consistency

> Trial Registry Records - Unit Label Consistency is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012333/call, status unknown (last checked 2026-10-25).

Validates that declared aggregate count kinds match unit labels within a single trial registry record (source/work/study/revision).

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/trial-registry-records/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012333/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trial-registry-records-unit-label-consistency-18c40d02
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CNPCyGpiE3JDwSTKy5bq2

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-unit-label-consistency-18c40d02 -d '<json body>'
```

Example prompt: Can you check this set of trial registry measurements for unit label consistency — I have up to 10 public measurement rows and I want to know if the declared aggregate count kinds actually match the unit labels in the record?

## When to prefer this

Choose this endpoint when you need to audit unit label consistency specifically within a single trial registry record (source/work/study/revision context) and your data is either public or synthetic. It is purpose-built for aggregate count kind vs. unit label cross-checking in trial registry contexts, unlike general schema validators or data quality tools that lack domain-specific unit semantics.

## Known failure modes

- measurements array empty or exceeds 32 items — rejected with validation error
- nonpersonalMetadata not set to true — request refused
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- malformed measurement objects in array — parsing error
- ambiguous unit labels that cannot be resolved — partial or failed analysis

## How this service works

Check declared aggregate count kinds against unit labels in one exact source/work/study/revision Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an analysis of whether declared aggregate count kinds are consistent with unit labels in the supplied record, including identified mismatches or confirmation of consistency. This is a supplied-record analysis, not independent certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trial-registry-records-unit-label-consistency-18c40d02/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)