# Bibliographies - Unit-Label Consistency Check

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

Validates that declared aggregate count types match their unit labels within a single supplied bibliography, source, work, study, or revision record.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/bibliographies/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012339/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bibliographies-unit-label-consistency-check-27c20515
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vR72OyfaKNZ6kQiVxzTDX

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 bibliographies-unit-label-consistency-check-27c20515 -d '<json body>'
```

Example prompt: Can you check this bibliography record for unit-label consistency — make sure all the declared aggregate count types match their unit labels? It's public data, nonpersonal metadata only, and I have 5 measurements to supply.

## When to prefer this

Choose this endpoint when you need a fast, per-record unit-label consistency check on a single bibliography, study, or revision artifact — particularly for pre-submission QA, research handoff validation, or data pipeline quality gates where the data is either public or synthetic and contains no personal metadata. Not suited for independent certification or cross-record bulk audits.

## Known failure modes

- measurements array empty or exceeds 32-item limit — validation error returned
- dataClass value not in allowed enum (public, synthetic) — schema rejection
- nonpersonalMetadata not set to true — request rejected
- Malformed measurement objects cause parsing failure
- Service unavailable returns HTTP 5xx with no report

## 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 a structured analysis report flagging any discrepancies between declared aggregate count kinds and their unit labels within the supplied record, along with details of the measurements inspected. Note: 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/bibliographies-unit-label-consistency-check-27c20515/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)