# Robotics Telemetry - Revision Delta Map

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

Enumerates owner, subject, revision, content, and scope pin changes between two supplied sets of robotics telemetry records, identified by stable record ID.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/revision-delta-map?utm_source=zero.xyz
- Price: $0.021325/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robotics-telemetry-revision-delta-map-b01935e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NP7F9rIhLFefjaPddtzTM

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

Example prompt: Compare these two sets of robotics telemetry records — up to 30 entries each in the before and after arrays — using public data class, and tell me exactly which owner, subject, revision, content, and scope pins changed between the two revisions.

## When to prefer this

Choose this endpoint when you need to compare two specific snapshots of robotics telemetry records and enumerate exactly which pins (owner, subject, revision, content, scope) changed between them. It is best suited for audit trails, change detection in calibration or frame data, and versioned telemetry diffing — particularly when you have pre/post record sets and want a stable-ID-keyed delta map rather than raw record export or validation.

## Known failure modes

- Record sets exceeding 32 items will be rejected
- Missing or mismatched stable record IDs may produce incomplete delta output
- Invalid dataClass enum value returns validation error
- nonpersonalMetadata must be explicitly set to true or the request is rejected
- Empty before/after arrays produce no delta output
- Malformed record structures may cause partial or failed analysis

## How this service works

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

## Output

A structured delta map enumerating changes in owner, subject, revision, content, and scope pins between the two supplied record sets, keyed by stable record ID. The result reflects changes found in the supplied records only and does not constitute independent certification.

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