# Technical Manuals — Record Sequence Diff

> Technical Manuals — Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035038/call, status unknown (last checked 2026-10-19).

Compares two ordered lists of procedure steps, identifying inserted, deleted, and reordered steps across before/after sequences with pinned digest tracking.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/technical-manuals/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035038/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-record-sequence-diff-47bed8ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4bOzF0KlLqNBURxD26f6I

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-record-sequence-diff-47bed8ec -d '<json body>'
```

Example prompt: Compare these two procedure step sequences from our equipment calibration manual — the before list has 8 steps and the after list has 10 steps — and tell me which steps were newly inserted versus just reordered, treating everything as public data.

## When to prefer this

Choose this endpoint when you need to precisely distinguish between newly inserted procedure steps and steps that were merely reordered across two sequential versions of a technical manual or procedure document, without needing execution planning or safety analysis. It is especially suited for offline, typed, non-personal metadata scenarios involving public or synthetic data classifications. Use it over generic text diff tools when step-level identity and digest pinning matter.

## Known failure modes

- Input arrays exceed 32-item limit — request rejected
- nonpersonalMetadata field not set to true — request rejected
- dataClass not set to 'public' or 'synthetic' — validation error
- Malformed step entries that cannot be parsed — diff may be incomplete
- Empty before and after arrays — returns empty diff with no meaningful output

## How this service works

Compare supplied procedure-step order and pinned digests across extracts. Inserted steps are distinct from reordered shared steps; no execution plan or safety assessment. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff of the two step sequences, distinguishing inserted steps (new, not present in before) from deleted steps (present in before but not after) and reordered shared steps (present in both but at different positions), along with pinned digest comparisons. No execution plan or safety assessment is included. Results retained for 24 hours; minimal receipt metadata retained for 90 days.

## 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/technical-manuals-record-sequence-diff-47bed8ec/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)