# Alloy Measurements - Record Sequence Diff

> Alloy Measurements - Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035194/call, status unknown (last checked 2026-10-25).

Separates true record insertions/deletions from shared-record reordering in alloy measurement datasets, preserving sequence integrity without conflating order changes with content changes.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035194/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-record-sequence-diff-45bf86a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PsZ8jGDs0kX66U-KcOFJ1

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-record-sequence-diff-45bf86a0 -d '<json body>'
```

Example prompt: Compare these two lists of alloy measurement records — the before snapshot has 12 records and the after snapshot has 14 — and tell me which records were actually inserted or deleted versus which ones just moved positions; the data is synthetic.

## When to prefer this

Use this endpoint when you need to audit two sequential snapshots of alloy measurement records and must distinguish genuine insertions/deletions from reordering of surviving records. Prefer this over generic diff tools when working with alloy lot, method, or composition-basis supplied-record datasets where positional drift must not be conflated with content change.

## Known failure modes

- Array exceeds 32-item limit per side — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true — request rejected
- Malformed array items — schema validation failure
- Network timeout for large but valid payloads

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for alloy lot/method/composition-basis Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured breakdown distinguishing actual record insertions and deletions from positional reorderings, so that surviving records can be confirmed unchanged in content even if their sequence index shifted.

## 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-record-sequence-diff-45bf86a0/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)