# Spectrometry Records - Record Sequence Diff

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

Diffs two ordered lists of spectral data points to separate true additions, deletions, and value changes from mere reordering, while also flagging non-increasing axis order and mismatched units.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/spectrometry-records/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035176/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spectrometry-records-record-sequence-diff-4d48f2d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5uPijKa8CcxsiiQwSyUSF

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

Example prompt: Compare these two wavelength spectrum arrays in nanometres with AU intensity units — tell me which points were genuinely added, removed, or changed versus just reordered, and flag any non-increasing axis issues. Both datasets are synthetic and non-personal.

## When to prefer this

Use this endpoint when you need to rigorously distinguish real spectral data mutations (additions, deletions, value changes) from mere reordering in scientific spectrometry records, and when you also need axis-order and unit validation in a single pass. Prefer it over generic diff tools when your data uses mass-to-charge, wavelength, or wavenumber axes with specific scientific unit semantics.

## Known failure modes

- Array exceeds 32 items — request rejected with validation error
- Invalid axis/axisUnit combination (e.g. wavelength with m/z) — may produce error or unexpected results
- nonpersonalMetadata not set to true — rejected by schema validation
- Mismatched or unsupported unit enums — validation error
- Empty before and after arrays — returns empty diff with no changes detected

## How this service works

Separate added/removed/changed spectral points from reordering of surviving point IDs; report non-increasing axis order and mismatched units within each supplied Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured breakdown separating added, removed, and value-changed spectral points from pure reordering of surviving point IDs; also reports any non-increasing axis order violations and unit mismatches within the supplied records. This is a supplied-record analysis, not independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "axis": {
   "enum": [
    "mass-to-charge",
    "wavelength",
    "wavenumber"
   ],
   "type": "string"
  },
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "axisUnit": {
   "enum": [
    "m/z",
    "nanometres",
    "inverse-centimetres"
   ],
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "intensityUnit": {
   "enum": [
    "counts",
    "AU"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/spectrometry-records-record-sequence-diff-4d48f2d3/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)