# BRAINIAC Perimeter Breach Signal Detector

> BRAINIAC Perimeter Breach Signal 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 physical security event logs to detect and correlate perimeter breach signals from sensors, cameras, and access control systems

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/physical-security/perimeter-breach-signal-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-perimeter-breach-signal-detector-9da6a32e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HUkc-einPuTB7_IAbvHJK

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-perimeter-breach-signal-detector-9da6a32e -d '<json body>'
```

Example prompt: I have a batch of physical security events from our north perimeter fence — beam sensors and PIR detectors both alarmed within 20 seconds of each other in zone north-fence. Can you analyze these events and tell me if there are any perimeter breach signals, what the confidence is, and which events are involved?

## When to prefer this

Use this endpoint when you have structured physical security event logs (sensor alarms, door events, camera triggers, IoT device readings) and need to automatically detect and correlate perimeter breach signals without deploying on-premise software. It is especially valuable for pay-per-call, no-account usage via x402/USDC on Base, for agentic pipelines that need breach signal detection as a composable step, or when you want clear separation between observed facts and inferred threats. Prefer this over generic LLM analysis when you need structured, schema-defined breach signal outputs with confidence scores and evidence trails.

## Known failure modes

- No events provided — returns empty items array with status 'none'
- Insufficient corroborating signals — single alarm events may return low confidence or no detection
- Missing required fields in event objects — partial analysis with available data
- Malformed event timestamps — events may be excluded from temporal correlation
- Input exceeds maxLength limits — request rejected or truncated
- Ambiguous zone/device IDs — signals may not be properly grouped by zone

## 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 items array of detected breach signal objects, each containing an ID, title, status, firstAt/lastAt timestamps, confidence level (low/medium/high), observed facts, inferred threat description, related event IDs, reasons for detection, evidence array with per-event inferences, and a confirmedIncident boolean. Also includes a top-level status, findings array with breach codes and details, checkedAt timestamp, itemCount, and limitations disclaimers about what the system did and did not do.

## 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": "perimeter-north_fence-P1",
    "title": "Possible perimeter breach signal",
    "lastAt": "2026-11-04T20:10:20.000Z",
    "source": "Caller-supplied perimeter events; local correlation",
    "status": "signal",
    "firstAt": "2026-11-04T20:10:00.000Z",
    "reasons": [
     "perimeter_alarm",
     "multi_sensor_zone",
     "breach_wording"
    ],
    "detector": "perimeter-breach-signal-detect",
    "evidence": [
     {
      "at": "2026-11-04T20:10:00.000Z",
      "fact": "intrusion_alarm; device=beam-1; zone=north-fence; outcome=alarm; msg=beam trip",
      "eventId": "P1",
      "inference": "Perimeter signal only; physical confirmation not performed.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:10:20.000Z",
      "fact": "intrusion_alarm; device=pir-2; zone=north-fence; outcome=alarm; msg=climb suspected",
      "eventId": "P2",
      "inference": "Perimeter signal only; physical confirmation not performed.",
      "confidence": "medium"
     }
    ],
    "confidence": "medium",
    "observedFacts": [
     "2 perimeter alarm/breach-style event(s).",
     "2 devices alarmed in zone north_fence.",
     "Event message/labels include breach/cut/climb/tamper wording."
    ],
    "inferredThreat": "Perimeter sensor alarms may indicate intrusion attempts; not a confirmed breach by themselves.",
    "relatedEventIds": [
     "P1",
     "P2"
    ],
    "confirmedIncident": false
   }
  ],
  "status": "detected",
  "findings": [
   {
    "code": "perimeter_breach",
    "kind": "conflict",
    "detail": "Perimeter indicators: perimeter_alarm, multi_sensor_zone, breach_wording (confirmedIncident=false).",
    "subject": "north_fence"
   }
  ],
  "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."
  ],
  "apiKeyRequired": false,
  "networkAc
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-perimeter-breach-signal-detector-9da6a32e/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)
