# BRAINIAC Physical Security Sensor Event Anomaly Detector

> BRAINIAC Physical Security Sensor Event Anomaly Detector 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 a stream of physical-security sensor events to detect anomalies such as threshold exceedances, baseline deviations, and fault signals — returning structured findings with confidence scores and inferred threats.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/physical-security/sensor-event-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-physical-security-sensor-event-anomaly-detector-1114a94a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_igt7N39lt3ckaA-Hsx88t

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-physical-security-sensor-event-anomaly-detector-1114a94a -d '<json body>'
```

Example prompt: Analyze these building sensor events for anomalies — I've got readings from device temp-1 showing 48°C against a baseline of 21°C, plus some door-held and alarm events from zone B2 today, and I want to know if anything looks like a real security or equipment issue.

## When to prefer this

Use this endpoint when you have caller-supplied physical security or IoT sensor event logs and need fast, deterministic anomaly detection without integrating a live physical security platform. It is ideal for offline or batch analysis of telemetry, log review workflows, or when you want structured threat hypotheses with explicit confidence scores and fact/inference separation — without requiring API keys or external data subscriptions. It is not appropriate if you need real-time device control, live feed integration, or confirmed incident classification without multi-signal evidence.

## Known failure modes

- Missing or malformed event data returns empty anomaly results rather than an error
- Events with no values, baselines, or thresholds may produce no findings due to insufficient signal
- Truncated or oversized payloads may be rejected if they exceed the 200,000 character input limit
- Ambiguous or unlabeled event categories may be classified as 'other', reducing detection accuracy
- No baseline supplied means deviation-based anomaly rules cannot fire, limiting detection coverage

## 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 containing a list of anomaly items — each with a title, first/last timestamp, detector name, confidence level, observed facts, inferred threat hypothesis, related event IDs, and whether it constitutes a confirmed incident — plus a findings array with structured codes and details, aggregate anomaly standard deviation, and a set of limitations clarifying that no physical systems are contacted or controlled.

## 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": "sensor-anomaly-temp_1",
    "title": "Sensor telemetry anomaly",
    "lastAt": "2026-11-04T20:15:00.000Z",
    "source": "Caller-supplied sensor telemetry; local anomaly rules",
    "status": "signal",
    "firstAt": "2026-11-04T20:15:00.000Z",
    "reasons": [
     "threshold_exceeded",
     "baseline_deviation",
     "explicit_anomaly_label"
    ],
    "detector": "sensor-event-anomaly-detect",
    "evidence": [
     {
      "at": "2026-11-04T20:15:00.000Z",
      "fact": "temperature; device=temp-1; value=48C",
      "eventId": "S4",
      "inference": "Sensor anomaly is a telemetry indicator, not a confirmed physical incident.",
      "confidence": "medium"
     }
    ],
    "confidence": "medium",
    "observedFacts": [
     "Device temp_1 value 48 met/exceeded threshold 30.",
     "Value 48 deviates ≥50% from baseline 21.",
     "Event S4 carries anomaly/fault wording or labels."
    ],
    "inferredThreat": "Unusual sensor values may indicate equipment fault, environmental change, or security-relevant disturbance.",
    "relatedEventIds": [
     "S4"
    ],
    "confirmedIncident": false
   }
  ],
  "status": "detected",
  "findings": [
   {
    "code": "sensor_anomaly",
    "kind": "conflict",
    "detail": "Sensor anomalies: threshold_exceeded, baseline_deviation, explicit_anomaly_label (confirmedIncident=false).",
    "subject": "temp_1"
   }
  ],
  "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 contacted and devices are never controlled.",
   "Temporal correlation and anomaly rules run locally over supplied records. Missing values are not invented.",
   "Observed facts are separated from inferred threat hypotheses. Anomalies are not labeled confirmed physical incidents without sufficient multi-signal evidence.",
   "Configurable windows/thresholds apply only when supplied; otherwise documented defaults are used.",
   "No paid physical-security feed is used and no API key is required."
  ],
  "anomalyStdev": 3,
  "apiKeyRequired": false,
  "networkAccessed": false,
  "deviceControlled": false,
  "paidProviderUsed": false,
  "physicalSystemConnected": false,
  "confirmedIncidentClaimed": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-physical-security-sensor-event-anomaly-detector-1114a94a/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)
