# Technical Manuals Revision Delta Map

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

Compares two versions of a technical manual's procedure projections to identify changed models, source pages, and procedure digests, flagging unchanged edition pins and changed step identities.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/technical-manuals/revision-delta-map?utm_source=zero.xyz
- Price: $0.021294/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/technical-manuals-revision-delta-map-bf19c7d5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GBFv82BTA3_bQci4ZiWbB

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 technical-manuals-revision-delta-map-bf19c7d5 -d '<json body>'
```

Example prompt: I have two snapshots of our maintenance manual — the old version and the new one — can you generate a revision delta map comparing them as public data so I can see exactly which procedure digests, source pages, and step identities changed and which edition pins stayed the same?

## When to prefer this

Choose this endpoint when you need a precise, typed diff of two technical manual procedure projections — specifically to identify changed procedure digests, source pages, model references, and step identities without semantic interpretation. Prefer this over general document diffing tools when working with structured procedure metadata and when you need explicit flagging of unchanged edition pins. Best suited for offline, nonpersonal metadata comparison with no need for content interpretation.

## Known failure modes

- Missing 'before' or 'after' object returns validation error
- nonpersonalMetadata not set to true results in rejection
- dataClass not set to 'public' or 'synthetic' causes schema validation failure
- Malformed procedure projection objects may return empty delta with no changes flagged
- Results expire after 24 hours; stale result retrieval is not supported

## How this service works

Compare two pinned procedure projections for changed model, source page and procedure digest. Flags unchanged edition pins and changed step identities without interpreting instruction meaning. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured delta map identifying: which procedure digests changed between the two projections, which source pages changed, which model identifiers changed, which edition pins remain unchanged, and which step identities changed — without interpreting the content or meaning of the instructions themselves.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/technical-manuals-revision-delta-map-bf19c7d5/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)