# Optical Measurements - Record Sequence Diff

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

Detects true record insertions and deletions in optical measurement datasets by separating structural record changes from mere reordering of surviving records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/optical-measurements/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035212/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/optical-measurements-record-sequence-diff-43a1ed72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_59Lqywl6-yUPS2ERPPXjk

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 optical-measurements-record-sequence-diff-43a1ed72 -d '<json body>'
```

Example prompt: I have two versions of an optical calibration record list — the before list has 5 records and the after list has 6 records — both classified as synthetic data. Can you diff them to tell me which records were genuinely inserted or deleted versus just reordered?

## When to prefer this

Choose this endpoint when you need to distinguish genuine record insertions and deletions from mere reordering within optical measurement, calibration, geometry, or lot/method-pinned record sets. It is specifically designed for supplied-record analysis of optical domain data (not thermal, spectrometry, or terrain), and is ideal when record identity must be preserved across sequence changes and the analysis is on caller-supplied synthetic or public data rather than live certified measurements.

## Known failure modes

- Array exceeds 32 items — request rejected with validation error
- nonpersonalMetadata not set to true — schema validation fails
- dataClass not one of 'public' or 'synthetic' — enum validation error
- Empty or malformed array items — may produce empty or unexpected diff output
- Network or payment failure via x402 protocol — request not processed

## How this service works

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

## Output

Returns a structured diff identifying records that were inserted (present in 'after' but not 'before') and records that were deleted (present in 'before' but not 'after'), explicitly separated from reordering of surviving records, for supplied optical measurement record sequences.

## 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/optical-measurements-record-sequence-diff-43a1ed72/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)