# Material Measurement Revision Diff

> Material Measurement Revision Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010068/call, status unknown (last checked 2026-11-02).

Compares two declared measurement revisions for a material field-by-field, separating value changes from changes in method, unit, and temperature.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/materials/revision-diff?utm_source=zero.xyz
- Price: $0.010068/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/material-measurement-revision-diff-19f2c9f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ezSq_z5UdeRAgnHUTn0wD

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 material-measurement-revision-diff-19f2c9f1 -d '<json body>'
```

Example prompt: Compare these two material measurement revisions — rev-001 as the before and rev-002 as the after — and show me which fields changed in value versus which changed in method, unit, or temperature. The data is public and contains no personal metadata.

## When to prefer this

Use this endpoint when you need a structured, field-level comparison of two specific material measurement revisions and want the diff explicitly categorized by change type (value, method, unit, temperature). Prefer this over generic diff tools when working with typed scientific measurement metadata where distinguishing why a value changed (e.g., different unit vs. different result) is critical. Suitable only for public or synthetic data classes with no personal metadata.

## Known failure modes

- Missing or malformed before/after revision objects returns a validation error
- Invalid dataClass enum value (not 'public' or 'synthetic') causes rejection
- nonpersonalMetadata not set to true causes request rejection
- Revision identifiers not matching any stored revision return a not-found error
- Attempting to diff incompatible data structures may return a schema mismatch error
- Result retrieval after 24-hour window returns expired/not-found response

## How this service works

Compare two declared measurement revisions field by field, separating value changes from changed method, unit and temperature. No inference of equivalent experiments. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured field-by-field diff of the two measurement revisions, with changes categorized into: value changes, method changes, unit changes, and temperature changes. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object"
  },
  "before": {
   "type": "object"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "afterRevision": {
   "type": "string"
  },
  "beforeRevision": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/material-measurement-revision-diff-19f2c9f1/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)