# Robotics Telemetry — Record Sequence Diff

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

Compares two ordered lists of declared robotics telemetry-message metadata (hashes and sequences) to identify added, removed, changed, and reordered messages offline.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035224/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robotics-telemetry-record-sequence-diff-346f6bcf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Axs7gmzrcr9mkzqgskoAx

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 robotics-telemetry-record-sequence-diff-346f6bcf -d '<json body>'
```

Example prompt: Can you diff these two robotics telemetry message sequences for me — I have a 'before' list and an 'after' list of declared message hashes and want to know exactly which messages were added, removed, changed, or reordered? Both lists are public, non-personal metadata.

## When to prefer this

Choose this endpoint when you need an offline, structured diff of two declared robotics telemetry message orderings using only typed metadata — no live robot connection, streaming, or timing analysis required. It is specifically suited for audit, regression testing, or schema reconciliation workflows where both the before and after sequences are available as static arrays of up to 32 items each and the data is classified as public or synthetic non-personal metadata.

## Known failure modes

- Sequence arrays exceeding 32 items will be rejected with a validation error
- dataClass values other than 'public' or 'synthetic' will fail schema validation
- nonpersonalMetadata must be exactly true; omitting or setting false will be rejected
- Empty or malformed hash entries in the before/after arrays may produce incomplete diff results
- Results older than 24 hours are no longer recoverable from retained storage

## How this service works

Compare two declared telemetry-message orders and hashes for added, removed, changed and reordered messages. No live telemetry capture, timing causality or robot control. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff identifying messages that were added (present in after but not before), removed (present in before but not after), changed (same position but different hash), and reordered (same message appearing at a different index) between the two supplied sequence arrays. Results are retained for 24 hours; minimal receipt metadata is kept 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/robotics-telemetry-record-sequence-diff-346f6bcf/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)