# License Records - Unit-Label Consistency Check

> License Records - Unit-Label Consistency Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012308/call, status unknown (last checked 2026-11-04).

Compares declared usage-allowance unit labels within a pinned license record frame to detect conflicting or incompatible label representations, without performing unit conversion or inferring equivalence.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/license-records/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012308/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/license-records-unit-label-consistency-check-d8b42c4a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2Wx2oDmZxo6CDSd7psswk

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 license-records-unit-label-consistency-check-d8b42c4a -d '<json body>'
```

Example prompt: Can you check these public license records for conflicting usage-allowance unit labels? I have up to 20 measurement entries and I need to know if any labels disagree — all data is nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need a lightweight, offline check for unit-label conflicts within a pinned license or permission-manifest frame using only public or synthetic nonpersonal metadata. It is appropriate when you do not need unit conversion, rights clearance, legal advice, or authoritative license interpretation — only a structural comparison of declared labels for consistency.

## Known failure modes

- Submission of personal metadata (nonpersonalMetadata must be const true) causes rejection
- Array of measurements outside the 1–32 item bounds returns a validation error
- Invalid dataClass value (not 'public' or 'synthetic') causes schema rejection
- Missing required fields result in a 400-level error
- Conflicting labels may not be detected if records lack stable pin identifiers

## How this service works

Compare declared usage allowance labels within a pinned frame; no unit conversion or inferred equivalence for nonpersonal work and permission-manifest metadata. No authoritative license interpretation, rights clearance, agreement acceptance, royalty transfer or legal advice. Satisfied conditions are caller declarations only. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a consistency assessment indicating whether the declared usage-allowance unit labels within the submitted measurement records agree, along with details on any conflicting label pairs identified. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No unit conversion, equivalence inference, or authoritative legal interpretation is provided.

## 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/license-records-unit-label-consistency-check-d8b42c4a/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)