# BRAINIAC Robotics Telemetry Anomaly Detection

> BRAINIAC Robotics Telemetry Anomaly Detection is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-12).

Analyzes robotics telemetry samples, cycle data, and sensor readings to detect statistical anomalies using z-score and other methods, returning flagged outlier events with diagnostics.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/robotics-intelligence/telemetry-anomaly-detect?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-robotics-telemetry-anomaly-detection-69f19ff9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_b6KeamZH70Toi17bRvTy-

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 brainiac-robotics-telemetry-anomaly-detection-69f19ff9 -d '<json body>'
```

Example prompt: Can you analyze this batch of joint position telemetry samples from robot R1 and flag any readings that look statistically anomalous? Here's the CSV export of the /joint_states topic from the last 24 hours.

## When to prefer this

Choose this endpoint when you need fast, pay-per-call statistical anomaly detection on robotics telemetry data — especially ROS topic samples, cycle records, or industrial sensor readings — without setting up an account or running your own anomaly detection pipeline. It is well-suited for one-off audits, pre-deployment validation, or agent-driven monitoring workflows where data is already in CSV, JSON, or structured sample form. Prefer alternatives if you need live equipment connectivity, binary ROS bag decoding, or continuous streaming anomaly detection.

## Known failure modes

- Malformed or missing telemetry samples result in empty or zero-count results
- Binary .bag/.mcap files not decoded — must supply CSV/JSON topic exports instead
- z-score anomaly detection requires sufficient samples in the series to compute meaningful mean/stdev
- Timestamps in unrecognized formats may be ignored
- Input exceeding maxItems (5000 samples, 2000 cycles) will be truncated or rejected
- Missing required fields (fileBase64 when file object used) will cause validation errors

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with an array of analyzed telemetry items (each tagged with z-score, mean, stdev, and an anomalous boolean), a status field ('detected' or similar), structured findings with anomaly codes and details, a checkedAt timestamp, series and anomaly counts, and a list of data-source limitations (e.g., no live equipment connection, no binary bag decoding).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "required": [
    "fileBase64"
   ],
   "properties": {
    "role": {
     "type": "string",
     "maxLength": 80
    },
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "text/plain",
      "text/csv",
      "application/json",
      "application/octet-stream"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "files": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "fileBase64"
    ],
    "properties": {
     "role": {
      "type": "string",
      "maxLength": 80
     },
     "filename": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
     },
     "mediaType": {
      "enum": [
       "text/plain",
       "text/csv",
       "application/json",
       "application/octet-stream"
      ],
      "type": "string"
     },
     "fileBase64": {
      "type": "string",
      "maxLength": 12000000,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20
  },
  "cycles": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "source": {
      "type": "string",
      "maxLength": 200
     },
     "endedAt": {
      "type": "string",
      "maxLength": 40
     },
     "program": {
      "type": "string",
      "maxLength": 160
     },
     "robotId": {
      "type": "string",
      "maxLength": 80
     },
     "startedAt": {
      "type": "string",
      "maxLength": 40
     },
     "workcellId": {
      "type": "string",
      "maxLength": 80
     },
     "durationSec": {
      "type": "number",
      "maximum": 1000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 2000
  },
  "samples": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "at": {
      "type": "string",
      "maxLength": 40
     },
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "unit": {
      "type": "
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "at": "2026-11-01T10:00:15.000Z",
    "id": "S16",
    "mean": 0.2375,
    "field": "position[0]",
    "stdev": 0.47,
    "topic": "/joint_states",
    "value": 2,
    "source": "Caller-supplied",
    "zScore": 3.75,
    "robotId": "R1",
    "anomalous": true,
    "liveEquipmentConnected": false
   }
  ],
  "status": "detected",
  "findings": [
   {
    "code": "telemetry_anomaly",
    "kind": "conflict",
    "detail": "Sample z-score 3.75 is outside ±3 from the supplied series mean.",
    "subject": "S16"
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "limitations": [
   "ROS bag topic samples, schemas, cycles, downtime, OPC UA tags, PLC alarms, maintenance records, and protocol declarations are copied only from labeled fields or text/CSV/JSON exports supplied by the caller.",
   "No live industrial equipment connection is opened and no machine commands are issued.",
   "Binary .bag/.mcap files are not fully decoded here. Supply topic CSV/JSON exports or labeled sample rows. Missing values are not invented.",
   "Anomaly, cycle-time, downtime, and maintenance estimates use only supplied measurements and intervals.",
   "Protocol compatibility compares caller-supplied required versus available protocol names, versions, and features only. Protocol specifications are not invented."
  ],
  "seriesCount": 1,
  "anomalyCount": 1,
  "apiKeyRequired": false,
  "paidProviderUsed": false,
  "machineCommandsIssued": false,
  "liveEquipmentConnected": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-robotics-telemetry-anomaly-detection-69f19ff9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
