# Thermal Measurements - Record Sequence Diff

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

Computes the difference between two sequences of thermal measurement records, separating true record insertions/deletions from reorderings without conflating the two.

## Facts

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

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 thermal-measurements-record-sequence-diff-71a5a7f9 -d '<json body>'
```

Example prompt: I have two snapshots of thermal measurement records — the before list has 12 entries and the after list has 14 entries, both classified as synthetic data. Can you diff them to show me which records were actually inserted or deleted versus which ones just got reordered?

## When to prefer this

Use this endpoint when you need to distinguish genuine record insertions and deletions from mere reordering in thermal measurement datasets. It is specifically designed for thermal lot/method/revision-pinned exports and handles sequence-aware diffing that naive set comparison cannot. Prefer it over generic diff tools when the domain is thermal measurements and preserving the semantics of record identity across revisions is important.

## Known failure modes

- Array exceeds 32-item limit causing validation rejection
- dataClass not set to 'public' or 'synthetic' returns schema error
- nonpersonalMetadata not set to true causes request rejection
- Malformed record objects in before/after arrays cause parsing failure
- Empty or identical arrays may return a null/empty diff result

## How this service works

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

## Output

A structured diff indicating which records were inserted, which were deleted, and which surviving records were reordered — keeping true record-set changes distinct from sequence permutations in the thermal measurement data.

## 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/thermal-measurements-record-sequence-diff-71a5a7f9/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)