# Catalyst Measurements - Record Sequence Diff

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

Computes a sequence diff between two ordered lists of catalyst measurement records, separating true record insertions/deletions from reordering of surviving records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/catalyst-measurements/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035182/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/catalyst-measurements-record-sequence-diff-20bf6331
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ElRGKlGzPIDEASdYmjW-u

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 catalyst-measurements-record-sequence-diff-20bf6331 -d '<json body>'
```

Example prompt: Compare these two catalyst measurement record lists — the before list has 12 entries and the after list has 14 entries, both marked as public data — and tell me which records were genuinely inserted or deleted versus which just got reordered.

## When to prefer this

Choose this endpoint when you need to cleanly separate structural record changes (insertions and deletions) from positional reordering of surviving records in a catalyst measurement sequence. It is specifically designed for public or synthetic material-lot/method-pinned datasets and is not a general-purpose diff tool — prefer it when working within that scientific measurement domain and when nonpersonal metadata compliance is required.

## Known failure modes

- Array length exceeds maxItems:32 — request rejected with validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const) — request rejected
- Malformed array items — parsing error returned
- Empty or identical arrays may return a no-change result

## How this service works

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

## Output

Returns a structured diff indicating which records were inserted, which were deleted, and which surviving records were merely reordered — allowing the caller to distinguish genuine record-count changes from positional reshuffling within the sequence.

## 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/catalyst-measurements-record-sequence-diff-20bf6331/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)