# Settlement Receipts — Unit-Label Consistency

> Settlement Receipts — Unit-Label Consistency is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012301/call, status unknown (last checked 2026-10-19).

Compares asset, network, and decimal labels on settlement receipts against caller-provided denomination contract definitions to detect unit-label mismatches, without performing token-registry lookups, exchange-rate conversion, or financial accounting verdicts.

## Facts

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

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 settlement-receipts-unit-label-consistency-d1d94eca -d '<json body>'
```

Example prompt: I have 12 settlement receipts and the denomination contracts they should reference — can you check whether the asset, network, and decimal labels on the receipts are consistent with those contracts, using public data class and marking these as nonpersonal metadata?

## When to prefer this

Choose this endpoint when you need a purely offline, no-side-effect label consistency check between settlement receipt metadata and your own denomination contract definitions — specifically when you do NOT need token-registry lookups, live exchange rates, decimal normalization, or financial accounting conclusions. It is best suited for auditing batches of up to 32 receipts at a time with nonpersonal metadata and is cost-effective at $0.012 per call.

## Known failure modes

- Receipts array empty or exceeds 32-item limit — validation error returned
- Assets array empty or exceeds 32-item limit — validation error returned
- nonpersonalMetadata field not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — schema validation failure
- Malformed receipt or asset objects — parsing error
- Caller-supplied denomination contracts have missing fields — incomplete comparison result

## How this service works

Compare receipt asset/network/decimal labels with caller-provided denomination contracts. No token-registry lookup, exchange rate, decimal normalization or financial accounting verdict. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured report of label consistency findings for each supplied receipt, identifying where asset names, network identifiers, or decimal labels deviate from the caller-provided denomination contract definitions. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No token-registry lookups, exchange rates, decimal normalization, or financial accounting verdicts are included.

## Request schema (JSON Schema)

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

## More

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