# Thermal Measurements - Revision Delta Map

> Thermal Measurements - Revision Delta Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.021324/call, status unknown (last checked 2026-10-16).

Enumerates owner, subject, revision, content, and scope pin changes between two supplied revisions of thermal lot/method/revision-pinned records by stable record ID

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/thermal-measurements/revision-delta-map?utm_source=zero.xyz
- Price: $0.021324/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/thermal-measurements-revision-delta-map-15756e23
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Rxt6CHwXPYgOz4UlvvOg1

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-revision-delta-map-15756e23 -d '<json body>'
```

Example prompt: Compare my two thermal measurement record sets — the before set has IDs [rec001, rec002] and the after set has [rec001, rec002, rec003] — using public data class, and tell me what owner, subject, revision, content, and scope pin changes occurred between the two revisions.

## When to prefer this

Use this endpoint when you need to audit field-level changes between exactly two revision snapshots of thermal measurement records and require a stable-ID-keyed delta map. Prefer this over generic diff tools when the records are thermal lot/method/revision-pinned exports and you need structured enumeration of owner, subject, content, and scope pin changes specifically. Choose this over timestamp-based endpoints when you have explicit before/after record arrays rather than time windows.

## Known failure modes

- Before or after arrays exceed 32 items — request rejected with validation error
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const constraint) — schema validation error
- Empty or mismatched record IDs with no overlap — empty delta map returned
- Malformed record ID format in arrays — parsing or lookup error
- Payment not supplied or insufficient USDC — 402 payment required error

## How this service works

Enumerate owner, subject, revision, content and scope pin changes by stable record ID in two supplied revisions for thermal lot/method/revision-pinned export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A delta map keyed by stable record ID showing which fields (owner, subject, revision, content, scope pins) changed between the two supplied revision arrays, enabling precise audit of what mutated across thermal measurement dataset snapshots.

## 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-revision-delta-map-15756e23/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)