# Alloy Measurements - Unit-Label Consistency Check

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

Checks whether quantity/unit labels are compatible and non-conflicting within the same dataset/subject/run/method/revision/quantity frame for alloy measurement records, without performing numerical conversion.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/unit-label-consistency?utm_source=zero.xyz
- Price: $0.01232/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-unit-label-consistency-check-a8187a8b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__1YGlaNNyPK6RRuNv4lzw

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 alloy-measurements-unit-label-consistency-check-a8187a8b -d '<json body>'
```

Example prompt: Check my synthetic alloy measurement records — I have up to 20 entries and need to know if there are any conflicting or incompatible unit labels within the same dataset/run/method frame, without converting any values numerically.

## When to prefer this

Choose this endpoint when you need to audit alloy measurement records strictly for unit-label compatibility and conflicts within the same contextual frame (dataset/subject/run/method/revision/quantity), without any need for numerical unit conversion. It is best suited for data quality checks on supplied records, not for converting measurements or certifying results independently.

## Known failure modes

- measurements array empty or exceeds 32 items — rejected with validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- malformed measurement objects in array — partial or full rejection
- ambiguous unit labels that cannot be resolved within the frame — flagged but not converted

## How this service works

Check quantity/unit compatibility and conflicting unit labels only within the same dataset/subject/run/method/revision/quantity frame; never convert numerically for alloy measurement Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an analysis of the supplied alloy measurement records indicating whether quantity/unit label pairs are compatible and whether any conflicting unit labels exist within the same dataset/subject/run/method/revision/quantity frame. Does not perform numerical unit conversion — purely a label-level consistency assessment.

## 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/alloy-measurements-unit-label-consistency-check-a8187a8b/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)