# BRAINIAC Physical Security Access Tailgating Signal Detect

> BRAINIAC Physical Security Access Tailgating Signal Detect 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).

Analyzes access control and sensor event logs to detect potential tailgating incidents using temporal correlation and anomaly rules

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/physical-security/access-tailgating-signal-detect?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-access-tailgating-signal-detect-c946b775
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hAckuUTAge_zZXp55kQOM

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-access-tailgating-signal-detect-c946b775 -d '<json body>'
```

Example prompt: Look at these access control events from our lobby door today and tell me if there are any tailgating signals — I have badge scan records showing one grant at 20:00:00 for user A1, then a second door passage at 20:00:04 without a badge, and a PIR sensor at pir-lobby showing 2 people at 20:00:05.

## When to prefer this

Use this endpoint when you have structured access control event logs (badge reads, door open/close, motion/PIR sensors, people-count data) and need to identify potential tailgating or piggybacking incidents without integrating a full physical security platform. It is well-suited for post-hoc log analysis, security audits, and agent-driven security workflows where you can supply raw event data and want actionable tailgating signals with supporting evidence and confidence scores, all without an ongoing subscription or account.

## Known failure modes

- Missing or malformed event timestamps cause timing correlation to fail
- Events lacking doorId or zone fields reduce detection accuracy
- Very small event windows with insufficient context produce low-confidence or no signals
- Occupancy/people-count fields absent from events disable people-count-based detectors
- Input exceeds maxLength limits causing request rejection
- No tailgating signals found returns empty items array with status not-detected

## 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 a list of tailgating signal items, each containing an ID, title, first and last seen timestamps, status, confidence level, observed facts, inferred threat description, supporting evidence events with their own confidence and inference notes, related event IDs, and a confirmedIncident boolean. Also includes top-level findings with codes and details, a checkedAt timestamp, item count, and a limitations section clarifying that inferences are based on caller-supplied data and no physical systems are contacted.

## 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": "tailgate-lobby-A1",
    "title": "Possible tailgating signal",
    "lastAt": "2026-11-04T20:00:05.000Z",
    "source": "Caller-supplied access/sensor events; local timing rules",
    "status": "signal",
    "firstAt": "2026-11-04T20:00:00.000Z",
    "reasons": [
     "ungated_second_passage",
     "motion_after_single_badge",
     "people_count_gt_badges"
    ],
    "detector": "access-tailgating-signal-detect",
    "evidence": [
     {
      "at": "2026-11-04T20:00:00.000Z",
      "fact": "access; door=lobby; zone=lobby; outcome=granted",
      "eventId": "A1",
      "inference": "Tailgating is inferred from timing correlation, not visually confirmed.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:00:04.000Z",
      "fact": "passage; door=lobby; zone=lobby",
      "eventId": "A2",
      "inference": "Tailgating is inferred from timing correlation, not visually confirmed.",
      "confidence": "medium"
     },
     {
      "at": "2026-11-04T20:00:05.000Z",
      "fact": "motion; device=pir-lobby; zone=lobby; value=2people",
      "eventId": "M1",
      "inference": "Tailgating is inferred from timing correlation, not visually confirmed.",
      "confidence": "medium"
     }
    ],
    "confidence": "medium",
    "observedFacts": [
     "Second door passage within 8s without badge/user id.",
     "1 motion/occupancy event(s) near a single badge grant.",
     "Occupancy/people-count ≥2 near a single grant."
    ],
    "inferredThreat": "Access plus nearby motion/second passage may indicate tailgating.",
    "relatedEventIds": [
     "A1",
     "A2",
     "M1"
    ],
    "confirmedIncident": false
   }
  ],
  "status": "detected",
  "findings": [
   {
    "code": "tailgating",
    "kind": "conflict",
    "detail": "Tailgating indicators: ungated_second_passage, motion_after_single_badge, people_count_gt_badges (confirmedIncident=false).",
    "subject": "lobby"
   }
  ],
  "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-signa
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-physical-security-access-tailgating-signal-detect-c946b775/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)
