# Robot Frame Tree Consistency Validator

> Robot Frame Tree Consistency Validator is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010074/call, status unknown (last checked 2026-10-15).

Validates a declared robot frame-parent tree for structural errors: multiple roots, missing parents, cycles, and self-links — without composing transforms or verifying coordinate values.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/robotics/frame-tree?utm_source=zero.xyz
- Price: $0.010074/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robot-frame-tree-consistency-validator-739b6484
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8qi34p0YTnsjmiOD1lXwn

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 robot-frame-tree-consistency-validator-739b6484 -d '<json body>'
```

Example prompt: Check this list of 12 robot frames and their declared parents for any cycles, missing parents, self-links, or multiple roots — the expected root is 'base_link' and this is synthetic data.

## When to prefer this

Choose this endpoint when you need a fast, offline structural check of a robot frame-parent declaration graph — specifically to catch topological errors (cycles, missing parents, multiple roots, self-links) without needing to evaluate transform math or coordinate correctness. Ideal for CI pipelines, pre-deployment validation, or debugging TF tree anomalies when you have typed metadata only and no live robot connection.

## Known failure modes

- Frame array exceeds 32 items — rejected with validation error
- Missing required 'nonpersonalMetadata: true' field — request rejected
- No frames provided (empty array) — rejected
- Expected root frame not found in declared frames — flagged as error or warning
- Malformed frame objects in array — schema validation failure
- Service unavailable or timeout — no result returned

## How this service works

Check a declared frame-parent tree for multiple roots, missing parents, cycles and self-links. Does not compose transforms or verify coordinate correctness. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured report indicating whether the declared frame tree is consistent, listing any detected issues such as cycles (with the frames involved), missing parent references, self-links (a frame pointing to itself), and multiple root frames. Does not evaluate transform correctness or numeric coordinate values.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robot-frame-tree-consistency-validator-739b6484/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)