# Alloy Measurements - Export Semantic Parity

> Alloy Measurements - Export Semantic Parity is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.03932/call, status unknown (last checked 2026-10-20).

Compares two sets of parsed typed record projections for alloy lot/method/composition-basis data, checking semantic parity (order-insensitive, pin-preserving) rather than raw-byte equality.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/export-semantic-parity?utm_source=zero.xyz
- Price: $0.03932/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-export-semantic-parity-3f050099
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E0Sln_u2JlxveZ2WcGM9O

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-export-semantic-parity-3f050099 -d '<json body>'
```

Example prompt: Compare these two sets of alloy measurement records — up to 32 entries each, before and after — and check if they're semantically equivalent (same pins and scope, ignoring order); treat the data as public and non-personal.

## When to prefer this

Use this endpoint when you need to verify that two sets of alloy measurement record projections are semantically equivalent (order-insensitive, pin-preserving) rather than byte-identical. Prefer this over generic diff tools when working with typed alloy lot, method, or composition-basis records where order may vary but semantic content must match. Not suitable for raw artifact certification or independent third-party validation.

## Known failure modes

- Arrays exceed 32-item limit — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true — request rejected
- Malformed record projections — parsing error returned
- Empty or missing required fields — schema validation failure

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for alloy lot/method/composition-basis Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment indicating whether the two supplied alloy record projection arrays are order-insensitively equivalent, with pins and scope preserved. Does not perform raw-byte comparison or certify the underlying artifact — result is an analytical comparison of the supplied records only.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "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-export-semantic-parity-3f050099/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)