# BRAINIAC Physical Security Alarm Correlation Analyzer

> BRAINIAC Physical Security Alarm Correlation Analyzer is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.05/call, status unknown (last checked 2026-11-12).

Correlates physical security alarm events across multiple sensors, doors, cameras, and devices to identify temporally clustered incidents and potential threats.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/physical-security/alarm-correlation-analyze?utm_source=zero.xyz
- Price: $0.05/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-alarm-correlation-analyzer-2b5d1a7f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aMhll6ReK8Y45yFdLH4j9

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-alarm-correlation-analyzer-2b5d1a7f -d '<json body>'
```

Example prompt: I have a log of physical security events from last night — door forced-open on lobby at 20:00, intrusion alarm from panel-1 at 20:00, and a motion alarm from cam-lobby at 20:02. Can you analyze whether these alarms are correlated and likely part of the same incident?

## When to prefer this

Choose this endpoint when you need to correlate raw physical security alarm events — from doors, cameras, sensors, IoT devices, and alarm panels — to detect whether clustered events represent a single incident. Ideal for SOC triage, post-incident review, or any workflow ingesting physical access and alarm logs. Prefer this over generic anomaly detection when your data includes structured security event fields like zone, deviceId, outcome, and category.

## Known failure modes

- Missing or malformed event timestamps cause correlation windows to fail
- No events provided results in empty items array with no findings
- Events with missing required fields (category, outcome) may reduce correlation accuracy
- Payloads exceeding 200,000 character limit for csv/json/text fields are rejected
- Confidence is 'medium' or 'low' when fewer than 3 correlated events are present
- Service does not contact physical security systems; missing data is not filled in

## 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 correlated alarm clusters ('items'), each including a cluster ID, title, first/last timestamps, confidence level, observed facts, inferred threat hypothesis, related event IDs, and whether a physical incident is confirmed. Also includes top-level status, findings with codes and details, the analysis timestamp, item count, and explicit limitations about what the service can and cannot determine.

## 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": "alarm-corr-A1",
    "title": "Correlated multi-sensor alarms",
    "lastAt": "2026-11-04T20:02:00.000Z",
    "source": "Caller-supplied alarms; local time-window correlation",
    "status": "signal",
    "firstAt": "2026-11-04T20:00:00.000Z",
    "reasons": [
     "multi_device_alarms",
     "cross_category_alarms"
    ],
    "detector": "alarm-correlation-analyze",
    "evidence": [
     {
      "at": "2026-11-04T20:00:00.000Z",
      "fact": "intrusion_alarm; device=panel-1; zone=lobby; outcome=alarm",
      "eventId": "A1",
      "inference": "Correlation groups alarms; does not confirm a physical incident.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:01:00.000Z",
      "fact": "forced_open; device=door-lobby; zone=lobby; outcome=forced",
      "eventId": "A2",
      "inference": "Correlation groups alarms; does not confirm a physical incident.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:02:00.000Z",
      "fact": "motion_alarm; camera=cam-lobby; outcome=alarm",
      "eventId": "A3",
      "inference": "Correlation groups alarms; does not confirm a physical incident.",
      "confidence": "medium"
     }
    ],
    "confidence": "high",
    "observedFacts": [
     "3 alarm-severity events within 15 minutes.",
     "Alarms across devices: panel-1, door-lobby, cam-lobby.",
     "Categories involved: alarm, door, camera."
    ],
    "inferredThreat": "Temporally clustered alarms may represent one incident spanning sensors.",
    "relatedEventIds": [
     "A1",
     "A2",
     "A3"
    ],
    "confirmedIncident": false
   }
  ],
  "status": "detected",
  "findings": [
   {
    "code": "alarm_correlation",
    "kind": "conflict",
    "detail": "Correlated alarms via multi_device_alarms, cross_category_alarms (confirmedIncident=false).",
    "subject": "A1"
   }
  ],
  "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
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-physical-security-alarm-correlation-analyzer-2b5d1a7f/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)
