# Spectrometry Records - Unit Label Consistency Check

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

Validates quantity/unit compatibility and flags conflicting unit labels within the same dataset/subject/run/method/revision/quantity frame for spectrometry records, without performing numerical conversion.

## Facts

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

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 spectrometry-records-unit-label-consistency-check-8c2eb8e5 -d '<json body>'
```

Example prompt: Check these 8 spectrometry measurements from a public dataset for any conflicting or incompatible unit labels within the same run and quantity frame — this is non-personal metadata only.

## When to prefer this

Use this endpoint when you need to catch unit labeling errors or incompatibilities within a bounded spectrometry dataset frame (same run, method, revision, quantity) before exporting spectral axis or intensity data. Prefer this over general data validation tools when your domain is specifically spectrometry records and you need frame-scoped unit label consistency checks without numerical conversion.

## Known failure modes

- Exceeds 32 measurements per call — request is rejected
- nonpersonalMetadata not set to true — validation fails
- Invalid or missing dataClass enum value — schema error
- Empty measurements array — minimum 1 item required
- Malformed measurement objects — missing required fields cause processing errors

## 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 spectral axis/intensity export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured report identifying unit label conflicts and quantity/unit incompatibilities found within the same dataset/subject/run/method/revision/quantity frame. Does not perform numerical unit conversion — only checks label consistency for the supplied spectrometry records.

## 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/spectrometry-records-unit-label-consistency-check-8c2eb8e5/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)