# Alloy Measurements Reference Integrity Map

> Alloy Measurements Reference Integrity Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035191/call, status unknown (last checked 2026-10-16).

Binds alloy measurement rows to exact supplied dataset lots, validating that each measurement row references and matches the declared material/lot/revision records without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/reference-integrity-map?utm_source=zero.xyz
- Price: $0.035191/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-reference-integrity-map-390d4358
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7D8lEo9mN-e5JgDDwyV_t

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-reference-integrity-map-390d4358 -d '<json body>'
```

Example prompt: Check reference integrity for these 12 alloy measurement rows against 3 lots I'll supply — this is a public dataset and all metadata is non-personal, so bind each row to its exact lot and tell me which ones don't match.

## When to prefer this

Choose this endpoint when you need to confirm that alloy measurement rows are correctly bound to specific supplied lots, revisions, or material records in a caller-controlled dataset — particularly for QA, traceability, or pre-publication integrity checks on public or synthetic alloy data. Not for independent third-party certification or live instrument data ingestion.

## Known failure modes

- Mismatched lot count if lots array references IDs not present in rows
- Rows array exceeds 32-item limit causing validation rejection
- dataClass not set to 'public' or 'synthetic' causing schema rejection
- nonpersonalMetadata not set to true causing request failure
- Partial binding results if rows reference lot IDs missing from the supplied lots array

## How this service works

Bind measurement rows to the exact supplied dataset/material/lot/revision/content Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A reference integrity map showing which measurement rows successfully bind to their declared lots and which do not, including any mismatches between supplied rows and lot/revision records, along with residual or unbound row details — scoped strictly to the caller-supplied dataset without independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lots": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "rows": {
   "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/alloy-measurements-reference-integrity-map-390d4358/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)