# Reading Plans - Unit Label Consistency Check

> Reading Plans - Unit Label Consistency Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.01234/call, status unknown (last checked 2026-10-16).

Validates that declared aggregate count kinds in a reading plan record match their corresponding unit labels within a single source, work, study, or revision entry.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/unit-label-consistency?utm_source=zero.xyz
- Price: $0.01234/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-unit-label-consistency-check-1a1c4788
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HMqrjVobH8uUN0KuX3ts9

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 reading-plans-unit-label-consistency-check-1a1c4788 -d '<json body>'
```

Example prompt: Can you check this reading plan record for unit label consistency — it has synthetic data, and I have 5 measurements I want validated to make sure the declared aggregate count kinds all match their unit labels?

## When to prefer this

Use this endpoint when you need to perform unit label consistency checks on a single reading plan, study, work, or revision record and want to validate that declared aggregate count kinds align with their unit labels. Best suited for data quality control pipelines where you supply the record for analysis rather than needing independent third-party certification.

## Known failure modes

- Measurements array outside 1–32 item bounds returns validation error
- dataClass not in ['public','synthetic'] enum causes rejection
- nonpersonalMetadata not set to true (const) causes request failure
- Malformed measurement objects may cause parsing errors
- Missing required fields result in 400-level errors

## 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 report indicating whether the declared aggregate count kinds in the supplied reading plan record are consistent with the unit labels, highlighting any mismatches or discrepancies found across the provided measurements. 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/reading-plans-unit-label-consistency-check-1a1c4788/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)