# BRAINIAC Trust Boundary Violation Detector

> BRAINIAC Trust Boundary Violation 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-14).

Analyzes data flows between system components across trust zones and identifies flows that cross trust boundaries without required security controls

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/security/trust-boundary-violation-detect?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-trust-boundary-violation-detector-2bb4cfcf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_w63HYHdNynW6MLxF5jNi3

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-trust-boundary-violation-detector-2bb4cfcf -d '<json body>'
```

Example prompt: Check my system architecture for trust boundary violations — I have two zones: 'trusted' at trust level 80 and 'public' at trust level 10, with an API service in the trusted zone sending PII data to a CDN in the public zone via flow 'f1', and I only have logging as a control — tell me what required controls are missing.

## When to prefer this

Use this endpoint when you need automated, structured detection of trust boundary violations in a software architecture described as a data flow graph — especially when doing threat modeling, compliance reviews, or pre-deployment security audits. It is ideal when you have explicit zone trust levels, components mapped to zones, and data flows with associated data classes and controls already defined. Prefer this over manual review when you have many flows to check at once (up to 2000). It does not scan live infrastructure — it reasons about your described architecture model only.

## Known failure modes

- Missing required fields (id, from_component_id, to_component_id, data_classes on flows, or id/trust_level on zones) returns a validation error
- Fewer than 2 zones provided fails minItems constraint
- More than 2000 flows or 100 zones exceeds maxItems limits
- Component references zone_id that doesn't exist in zones array may produce unexpected results
- No violations found returns an empty findings array with summary counts
- Payment failure via x402 returns HTTP 402 and no analysis is performed

## 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 summary of total flows analyzed and violation count, plus a findings array where each violation includes: the flow ID, severity (e.g. high), trust drop magnitude, from/to zone IDs and component IDs, the data classes involved, which required controls are present vs missing, human-readable evidence statements explaining why the violation was flagged, and a specific remediation recommendation. Also returns explanatory text about how the analysis works.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "flows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "from_component_id",
     "to_component_id",
     "data_classes"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "protocol": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "control_ids": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 120,
       "minLength": 1
      },
      "maxItems": 50
     },
     "data_classes": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 80,
       "minLength": 1
      },
      "maxItems": 20,
      "minItems": 1
     },
     "to_component_id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "from_component_id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 2000,
   "minItems": 1
  },
  "zones": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "trust_level"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "name": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
     },
     "trust_level": {
      "type": "integer",
      "maximum": 100,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 100,
   "minItems": 2
  },
  "controls": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "kind"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "kind": {
      "enum": [
       "encryption_in_transit",
       "encryption_at_rest",
       "authentication",
       "authorization",
       "network_policy",
       "tokenization",
       "logging",
       "other"
      ],
      "type": "string"
     },
     "flow_ids": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 120,
       "minLength": 1
      },
      "maxItems": 100
     },
     "zone_ids": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 120,
       "minLength": 1
      },
      "maxItems": 100
     },
     "component_ids": {
      "type": "array",
      "items": {
       "type":
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "summary": {
   "flows": 1,
   "violations": 1
  },
  "findings": [
   {
    "code": "trust_boundary_violation",
    "flow_id": "f1",
    "evidence": [
     "Flow f1 moves from zone trusted (trust 80) to zone public (trust 10).",
     "Required controls on trust drop: encryption_in_transit, authentication.",
     "…"
    ],
    "severity": "high",
    "to_zone_id": "public",
    "trust_drop": 70,
    "remediation": "Add encryption_in_transit, authentication on flow f1 or on the components/zones it crosses before allowing this data pa…",
    "data_classes": [
     "pii"
    ],
    "from_zone_id": "trusted",
    "to_component_id": "cdn",
    "missing_controls": [
     "encryption_in_transit",
     "authentication"
    ],
    "present_controls": [
     "logging"
    ],
    "from_component_id": "api"
   }
  ],
  "explanations": [
   "A trust-boundary violation is a flow from a higher trust_level zone to a lower one that lacks every required_controls_o…",
   "Controls are matched by flow_ids, component_ids, zone_ids, or flow.control_ids. No infrastructure is scanned."
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-trust-boundary-violation-detector-2bb4cfcf/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)
