# Robotics Telemetry Required Field Coverage Checker

> Robotics Telemetry Required Field Coverage Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010147/call, status unknown (last checked 2026-10-16).

Checks whether required fields are present across robotics telemetry dataset rows, returning null for each missing required field rather than treating absence as an error

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/required-field-coverage?utm_source=zero.xyz
- Price: $0.010147/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-required-field-coverage-checker-01d5023b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3wQps7ae71ZAtBTYWGaCJ

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-required-field-coverage-checker-01d5023b -d '<json body>'
```

Example prompt: Check these 10 rows of synthetic robotics telemetry data and tell me which of the required fields — 'robot_id', 'frame_timestamp', 'calibration_pin', and 'clock_revision' — are missing; flag nulls for absent ones rather than throwing errors.

## When to prefer this

Choose this endpoint when you need to audit robotics or scientific telemetry rows for required field presence before export or processing, and you want null-safe results (missing = null, not an error) rather than hard failures. Prefer it over general schema validators when working specifically with robot/frame/clock/calibration-pinned telemetry data that must remain non-personal and fits within the 32-row, 8-field constraints.

## Known failure modes

- rows array empty or exceeds 32 item limit — validation error
- requiredFields array empty or exceeds 8 item limit — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- malformed row objects that cannot be parsed — may return partial or error results
- network timeout on large row batches near the 32-row limit

## How this service works

Check presence of required scientific dataset/method/revision/content pins; null is missing, not an invalid credential or artifact for robot/frame/clock/calibration-pinned telemetry export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-row coverage report indicating the presence or absence (null) of each requested required field across the submitted telemetry rows, allowing callers to identify exactly which records are missing which mandatory fields without treating absence as an invalid credential or artifact error.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robotics-telemetry-required-field-coverage-checker-01d5023b/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)