# Robotics Telemetry Schema Directionality Validator

> Robotics Telemetry Schema Directionality Validator is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035223/call, status unknown (last checked 2026-10-16).

Compares closed export-field schema directionality guarantees for robotics telemetry records, validating field structure constraints against supplied data classes.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/schema-directionality?utm_source=zero.xyz
- Price: $0.035223/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-schema-directionality-validator-c5ae6942
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u4aXlBfMelSju7tRgypqs

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-schema-directionality-validator-c5ae6942 -d '<json body>'
```

Example prompt: Compare these two sets of robotics telemetry export fields — the before array has my old schema fields and the after array has the new ones — using the 'synthetic' data class, with nonpersonalMetadata set to true, and flag whether consumers are allowed extra fields.

## When to prefer this

Use this endpoint when you need to validate schema directionality changes specifically for robotics telemetry export fields — particularly when checking whether schema evolution breaks closed export-field guarantees. Prefer this over generic schema diff tools when working within the mahastrategies data governance framework for robotics/telemetry domains.

## Known failure modes

- Empty or invalid before/after arrays return a validation error
- Exceeding maxItems (32) on before or after arrays results in schema rejection
- Invalid dataClass enum value (not 'public' or 'synthetic') causes a bad request error
- nonpersonalMetadata not set to true (const:true) causes rejection
- Service unavailable or timeout if the endpoint is under load

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured analysis of schema directionality for the robotics telemetry export fields, indicating whether field removals, type changes, or weakened constraints exist between the before and after field sets, along with compliance status for the specified data class and metadata flags.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "consumerAllowsExtraFields": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robotics-telemetry-schema-directionality-validator-c5ae6942/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)