# BRAINIAC IoT Device Behavior Analyzer

> BRAINIAC IoT Device Behavior Analyzer 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 IoT device telemetry events to detect behavioral anomalies such as reporting gaps, unexpected reboots, unauthorized config changes, and other physical-security-relevant irregularities.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/physical-security/iot-device-behavior-analyze?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-iot-device-behavior-analyzer-b9135510
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OTSsa-dsxuUhAoqqZpvPb

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-iot-device-behavior-analyzer-b9135510 -d '<json body>'
```

Example prompt: Analyze these IoT event logs from our smart lock (device ID lock-7) and tell me if there are any behavioral anomalies — I'm seeing some unexpected reboots and config changes around 8pm last night and want to know if this looks like tampering or misconfiguration.

## When to prefer this

Use this endpoint when you have IoT or physical-security device telemetry and want automated behavioral anomaly detection — particularly for detecting reporting gaps, unexpected reboots, unauthorized configuration changes, or other device-level irregularities. It is especially useful in physical security contexts (smart locks, sensors, cameras, access control) where device misbehavior may signal tampering, compromise, or misconfiguration. Prefer this over generic log analysis tools when you need structured threat inferences with confidence scores and evidence chains, and when you want pay-per-call pricing with no account setup.

## Known failure modes

- Insufficient or malformed event data may produce no detections even when anomalies exist
- Very short time windows may not reveal reporting gaps that require longer baselines
- Confidence may remain 'medium' or 'low' if events lack enough contextual metadata
- Large event arrays exceeding schema limits may be rejected or truncated
- Ambiguous device IDs or missing timestamps may reduce detection accuracy
- False positives possible for devices with legitimately irregular reporting schedules

## 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 detected behavioral anomaly items, each including a title, first/last occurrence timestamps, detector ID, reasons for flagging, evidence entries with timestamps and inferences, confidence level, observed facts, inferred threat description, related event IDs, and whether a confirmed incident was declared. Also includes a top-level status, findings array with codes and details, a checkedAt timestamp, and a limitations section describing what the analysis cannot confirm.

## 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
  },
  "events": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "at": {
      "type": "string",
      "maxLength": 40
     },
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "unit": {
      "type": "string",
      "maxLength": 40
     },
     "zone": {
      "type": "string",
      "maxLength": 120
     },
     "value": {
      "type": "number",
      "maximum": 1000000000,
      "minimum": -1000000000
     },
     "doorId": {
      "type": "string",
      "maxLength": 120
     },
     "labels": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 80
      },
      "maxItems": 40
     },
     "source": {
      "type": "string",
      "maxLength": 200
     },
     "userId": {
      "type": "string",
      "maxLength": 120
     },
     "badgeId": {
      "type": "string",
      "maxLength": 120
     },
     "message": {
      "type": "string",
      "maxLength": 4000
     },
     "outcome": {
      "enum": [
       "gra
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "id": "iot-behavior-lock_7",
    "title": "Unusual IoT device behaviour",
    "lastAt": "2026-11-04T20:31:00.000Z",
    "source": "Caller-supplied IoT telemetry; local behavioural rules",
    "status": "signal",
    "firstAt": "2026-11-04T18:00:00.000Z",
    "reasons": [
     "reporting_gap",
     "unexpected_device_event"
    ],
    "detector": "iot-device-behavior-analyze",
    "evidence": [
     {
      "at": "2026-11-04T18:00:00.000Z",
      "fact": "heartbeat; device=lock-7; value=1",
      "eventId": "I1",
      "inference": "IoT behaviour anomaly only; device was not contacted or controlled.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T19:00:00.000Z",
      "fact": "heartbeat; device=lock-7; value=1",
      "eventId": "I2",
      "inference": "IoT behaviour anomaly only; device was not contacted or controlled.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:30:00.000Z",
      "fact": "reboot; device=lock-7; msg=unexpected reboot",
      "eventId": "I3",
      "inference": "IoT behaviour anomaly only; device was not contacted or controlled.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:31:00.000Z",
      "fact": "config_change; device=lock-7; msg=unauthorized config change",
      "eventId": "I4",
      "inference": "IoT behaviour anomaly only; device was not contacted or controlled.",
      "confidence": "medium"
     }
    ],
    "confidence": "medium",
    "observedFacts": [
     "Gap of ≈60 minutes between I1 and I2 (threshold 30m).",
     "Gap of ≈90 minutes between I2 and I3 (threshold 30m).",
     "Device event I3 indicates reboot/offline/config/unexpected behaviour.",
     "Device event I4 indicates reboot/offline/config/unexpected behaviour."
    ],
    "inferredThreat": "Unusual IoT reporting or control patterns can indicate misconfiguration, fault, or misuse.",
    "relatedEventIds": [
     "I1",
     "I2",
     "I3",
     "I4"
    ],
    "confirmedIncident": false
   }
  ],
  "status": "detected",
  "findings": [
   {
    "code": "iot_behavior",
    "kind": "conflict",
    "detail": "IoT behaviour indicators: reporting_gap, unexpected_device_event (confirmedIncident=false).",
    "subject": "lock_7"
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "itemCount": 1,
  "limitations": [
   "Physical/IoT event logs and telemetry are copied only from caller-supplied fields. Physical security systems are not co
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-iot-device-behavior-analyzer-b9135510/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)
