# Robotics Telemetry Export Semantic Parity Check

> Robotics Telemetry Export Semantic Parity Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.039325/call, status unknown (last checked 2026-10-16).

Compares two sets of parsed typed record projections from robot/frame/clock/calibration-pinned telemetry exports for semantic parity, ignoring field order while preserving all pins and scope.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039325/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robotics-telemetry-export-semantic-parity-check-89b6c2d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S48M9t6aBLmiJB87VpEEi

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-export-semantic-parity-check-89b6c2d6 -d '<json body>'
```

Example prompt: Compare these two sets of robot telemetry projections — up to 32 records each in the 'before' and 'after' arrays, both classified as synthetic data — and tell me if they are semantically equivalent, ignoring field order but preserving all frame and clock pins.

## When to prefer this

Choose this endpoint when you need to verify that two versions of robot telemetry record projections are semantically equivalent after a transformation, re-ordering, or pipeline stage — specifically when you care about pin-scope (frame, clock, calibration) preservation but not raw byte equality. Prefer it over raw diff tools when working with typed, structured telemetry records in robotic systems where field order may legitimately vary but semantic content must match.

## Known failure modes

- More than 32 items in before or after array returns validation error
- dataClass value outside 'public' or 'synthetic' enum is rejected
- nonpersonalMetadata not set to true causes request rejection
- Malformed or untyped record projections may cause parse errors
- Empty arrays on both sides may return trivial parity with no useful comparison

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for robot/frame/clock/calibration-pinned telemetry export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured report indicating whether the before and after sets of typed record projections are semantically equivalent, with details on any pin-scoped mismatches, missing fields, or ordering differences that affect meaning, while explicitly noting that this is a supplied-record comparison and not an independent certification of the underlying artifact.

## 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-export-semantic-parity-check-89b6c2d6/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)