# Robotics Telemetry Provenance Edge Audit

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

Binds declared edges to pinned endpoint nodes and owner/subject records, auditing provenance of robotics telemetry data graph connections.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045325/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-provenance-edge-audit-21e69151
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2qUuXspa8lRm70amaIuY8

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-provenance-edge-audit-21e69151 -d '<json body>'
```

Example prompt: Audit the provenance of these declared telemetry edges and nodes — classify the data as synthetic, and confirm nonpersonal metadata only — I need to verify the edge-to-endpoint bindings and owner/subject record linkages are correct.

## When to prefer this

Choose this endpoint when you need to audit or verify the provenance of declared graph edges in robotics telemetry datasets — specifically to confirm that edges are properly bound to pinned endpoint nodes and to owner/subject records. Suitable for record quality control on non-personal, public or synthetic telemetry data; not for live certification or independent third-party attestation.

## Known failure modes

- Missing or malformed edges/nodes array returns validation error
- edges or nodes arrays exceeding 32 items are rejected
- dataClass value outside 'public' or 'synthetic' enum causes schema rejection
- nonpersonalMetadata not set to true causes request rejection
- Ambiguous or unresolvable edge-node bindings may return partial or failed audit results
- Service unavailability returns HTTP 402/5xx with no audit result

## How this service works

Bind a declared edge to both pinned endpoints and the exact owner/subject Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit result indicating whether each declared edge is successfully bound to its pinned endpoint nodes and to the correct owner/subject supplied records, along with any binding failures or anomalies detected in the provenance chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nodes": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "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-provenance-edge-audit-21e69151/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)