# Tool Schemas — Unit-Label Consistency Check

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

Compares declared request and response coordinates in tool-schema declarations to detect unit-label inconsistencies, keeping UTF-8 bytes, codepoints, and tokens distinct without any tokenizer or remote execution.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012304/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-unit-label-consistency-check-f509e5e4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jxcv2xMQeWxwsCPwJVVdA

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 tool-schemas-unit-label-consistency-check-f509e5e4 -d '<json body>'
```

Example prompt: Can you check these tool schema contracts for unit-label consistency — I want to make sure the request and response coordinates are declaring bytes, codepoints, and tokens in a consistent and non-conflated way? The data is public metadata, nonpersonal only.

## When to prefer this

Choose this endpoint when you need to verify that tool-schema declarations maintain unit-label coherence across request and response coordinates specifically — particularly when working with schemas that distinguish UTF-8 bytes, codepoints, and tokens and you want to catch conflation before deployment. This is the right choice for offline, nonpersonal metadata validation of typed tool schemas without any tokenizer, conversion, or remote execution dependency. Prefer this over general-purpose schema validators when the specific concern is unit-label consistency rather than structural or type correctness.

## Known failure modes

- Submitting more than 32 contracts or observations in a single call returns a validation error
- Setting nonpersonalMetadata to false (or omitting the const:true) is rejected
- Providing an unsupported dataClass value other than 'public' or 'synthetic' causes a schema error
- Empty contracts or observations arrays are not accepted (minItems: 1)
- Network or payment failure may result in no result being returned and a 402 payment required error

## How this service works

Compare declared request/response coordinates for each tool-schema declaration. UTF-8 bytes, codepoints and tokens stay distinct; no tokenizer, conversion or remote execution. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A report indicating whether unit labels (UTF-8 bytes, codepoints, tokens) are used consistently across declared request/response coordinates in each submitted tool-schema. Highlights any mismatches or inconsistencies between coordinate declarations. Results are retained for 24 hours; minimal receipt metadata for 90 days.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tool-schemas-unit-label-consistency-check-f509e5e4/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)