Detect unusual door-access patterns API
Identify unusual access patterns from caller-supplied door-entry logs (denials, forced doors, held-open, after-hours). Not a confirmed intrusion.
The Detect unusual door-access patterns operation is part of the Physical & IoT Security API on BRAINIAC.software. Identify unusual access patterns from caller-supplied door-entry logs (denials, forced doors, held-open, after-hours). Not a confirmed intrusion. It is exposed as POST /api/v1/physical-security/door-access-pattern-detect and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied physical/IoT event logs and telemetry processed locally Limitations: Physical security systems are not contacted and devices are never controlled. Anomalies are not labeled confirmed physical incidents without sufficient multi-signal evidence. Temporal correlation and anomaly rules run locally over supplied records only. Missing telemetry values are reported as missing, not invented. No paid physical-security feed is used and no API key is required. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Detect sensor-event anomalies, Detect tailgating signals, Detect perimeter-breach signals, Detect camera-tampering signals. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/physical-security/door-access-pattern-detectExample request
curl -i -X POST "https://www.brainiac.software/api/v1/physical-security/door-access-pattern-detect" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"asOf": "2026-11-04T21:00:00.000Z",
"doorWindowMinutes": 60,
"events": [
{
"id": "D1",
"at": "2026-11-04T20:00:00.000Z",
"category": "door",
"doorId": "door-a",
"eventType": "access",
"outcome": "denied",
"badgeId": "B1",
"source": "Caller-supplied"
},
{
"id": "D2",
"at": "2026-11-04T20:01:00.000Z",
"category": "door",
"doorId": "door-a",
"eventType": "access",
"outcome": "denied",
"badgeId": "B1",
"source": "Caller-supplied"
},
{
"id": "D3",
"at": "2026-11-04T20:02:00.000Z",
"category": "door",
"doorId": "door-a",
"eventType": "access",
"outcome": "denied",
"badgeId": "B2",
"source": "Caller-supplied"
},
{
"id": "D4",
"at": "2026-11-04T20:03:00.000Z",
"category": "door",
"doorId": "door-a",
"eventType": "forced_open",
"outcome": "forced",
"source": "Caller-supplied"
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Detect sensor-event anomalies — $0.04 USDC
- Detect tailgating signals — $0.05 USDC
- Detect perimeter-breach signals — $0.04 USDC
- Detect camera-tampering signals — $0.04 USDC