# Api Contracts — Unit-label consistency

> Api Contracts — Unit-label consistency is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012303/call, status unknown (last checked 2026-10-19).

Compares declared request/response coordinates in HTTP contracts to verify that UTF-8 bytes, codepoints, and tokens are kept distinct and consistently labeled throughout the contract metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012303/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-unit-label-consistency-c4bedffa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8HQBh9Xnkc8CMyAdX1-rX

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 api-contracts-unit-label-consistency-c4bedffa -d '<json body>'
```

Example prompt: Can you check these API contracts for unit-label consistency — specifically make sure bytes, codepoints, and tokens are kept distinct in the request and response coordinates? The data is synthetic and nonpersonal.

## When to prefer this

Choose this endpoint when you need to audit HTTP API contract metadata specifically for unit-label consistency — ensuring bytes, codepoints, and tokens are never conflated in request/response coordinate declarations. It operates fully offline with no tokenizer, conversion, or remote execution, making it suitable for sensitive-but-nonpersonal contract metadata. Prefer it over general schema validators when the specific concern is dimensional unit labeling in API specs.

## Known failure modes

- Empty or malformed contracts array (minItems:1 not met)
- More than 32 contracts or observations submitted (maxItems exceeded)
- dataClass not set to 'public' or 'synthetic'
- nonpersonalMetadata not explicitly set to true
- Personal or non-public data submitted causing rejection
- Malformed contract declarations that cannot be parsed for coordinate comparison

## How this service works

Compare declared request/response coordinates for each HTTP contract. 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 identifying which declared request/response coordinates in the supplied HTTP contracts have inconsistent or conflated unit labels, distinguishing UTF-8 bytes, codepoints, and token counts as separate entities. Results are retained for 24 hours; 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/api-contracts-unit-label-consistency-c4bedffa/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)