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
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.
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.
POSThttps://www.brainiac.software/api/v1/security/trust-boundary-violation-detect?utm_source=zero.xyzUse 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.
| Field | Type | Description |
|---|---|---|
| flows | array | |
| zones | array | |
| controls | array | |
| components | array | |
| required_controls_on_trust_drop | array |
{
"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."
]
}
}No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"