# BRAINIAC Building Security Timeline

> BRAINIAC Building Security Timeline 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).

Builds a chronological, severity-annotated timeline from caller-supplied physical security events (door access, cameras, alarms, sensors, IoT) and surfaces anomalies, correlations, and findings.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/physical-security/building-security-timeline?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-building-security-timeline-69dbd16a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_K9IQ42jVqEiLPE7Yu3Te0

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-building-security-timeline-69dbd16a -d '<json body>'
```

Example prompt: I have a batch of building security logs from our HQ lobby covering November 4th — events include a door access denial, a camera lens-cover tamper alert, and an intrusion alarm — can you build a chronological security timeline, flag anomalies, and tell me if any of them look like a confirmed incident?

## When to prefer this

Choose this endpoint when you have caller-supplied physical security event data (door access logs, camera alerts, alarm events, IoT sensor readings) and need to sequence, correlate, and analyze them without connecting to live security infrastructure. It is ideal for post-incident reconstruction, routine log auditing, and anomaly detection over exported security data. Prefer this over generic log analysis tools when your data includes structured physical-security fields like doorId, badgeId, cameraId, outcome enums, and zone identifiers, and you need severity-annotated, categorized timeline output with explicit incident confirmation logic.

## Known failure modes

- Malformed or missing event timestamps cause sequencing errors or omitted events
- Events lacking required fields (category, outcome) may be classified as 'other' or 'unknown'
- Very large event arrays approaching the maxItems limit may be truncated
- Insufficient corroborating signals prevent confirmedIncident flags from being set — findings remain observations
- Input CSV or JSON that is malformed or exceeds maxLength limits will be rejected
- Ambiguous zone or building identifiers reduce grouping accuracy in section summaries

## 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 structured JSON object containing: a chronological timeline of normalized security events (each with timestamp, zone, building, category, severity, eventType, outcome, and confirmedIncident flag), a findings array with coded observations and anomaly detections, section summaries grouped by building and category, event counts, a checkedAt timestamp, and a limitations list clarifying that no live security systems are contacted and all analysis runs locally over caller-supplied data.

## 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": {
  "status": "reported",
  "findings": [
   {
    "code": "timeline_built",
    "kind": "observation",
    "detail": "Timeline includes 3 security-relevant event(s); none are confirmed incidents.",
    "subject": ""
   }
  ],
  "sections": [
   {
    "lastAt": "2026-11-04T20:00:00.000Z",
    "firstAt": "2026-11-04T19:50:00.000Z",
    "building": "hq",
    "categories": [
     "door",
     "camera",
     "alarm"
    ],
    "eventCount": 3
   }
  ],
  "timeline": [
   {
    "at": "2026-11-04T19:50:00.000Z",
    "zone": "lobby",
    "source": "Caller-supplied",
    "eventId": "E1",
    "outcome": "denied",
    "summary": "access; door=lobby; zone=lobby; outcome=denied",
    "building": "HQ",
    "category": "door",
    "deviceId": "lobby",
    "sequence": 1,
    "severity": "medium",
    "eventType": "access",
    "confirmedIncident": false
   },
   {
    "at": "2026-11-04T19:55:00.000Z",
    "zone": "lobby",
    "source": "Caller-supplied",
    "eventId": "E2",
    "outcome": "unknown",
    "summary": "tamper; camera=cam-lobby; zone=lobby; msg=lens covered",
    "building": "HQ",
    "category": "camera",
    "deviceId": "cam-lobby",
    "sequence": 2,
    "severity": "high",
    "eventType": "tamper",
    "confirmedIncident": false
   },
   {
    "at": "2026-11-04T20:00:00.000Z",
    "zone": "lobby",
    "source": "Caller-supplied",
    "eventId": "E3",
    "outcome": "alarm",
    "summary": "intrusion_alarm; device=panel-1; zone=lobby; outcome=alarm",
    "building": "HQ",
    "category": "alarm",
    "deviceId": "panel-1",
    "sequence": 3,
    "severity": "high",
    "eventType": "intrusion_alarm",
    "confirmedIncident": false
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "eventCount": 3,
  "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."
  ],
  "apiKeyRequired": false,
  "networkAccessed": false,
  "deviceControlled": false,
  "paid
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-building-security-timeline-69dbd16a/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)
