# BRAINIAC Sensitive Data Flow Audit API

> BRAINIAC Sensitive Data Flow Audit API 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-11).

Audits system architecture data flows for sensitive data handling violations, missing security controls, and zone policy breaches based on supplied handling rules.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/security/sensitive-data-flow-audit?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-sensitive-data-flow-audit-api-6b306a1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vA606EDeq3MHZGRXiuORl

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-sensitive-data-flow-audit-api-6b306a1e -d '<json body>'
```

Example prompt: Audit these data flows for sensitive data handling issues — I have one flow from a 'vault' component to a 'web' component carrying 'card_pan' data, the vault is in a PCI zone (trust level 90) and the web component is in an app zone (trust level 50), I have a handling rule requiring tokenization for card_pan, and the only control I've attached is encryption_in_transit. Tell me what violations exist and how to fix them.

## When to prefer this

Use this endpoint when you need a fast, schema-driven audit of a system's data flow architecture against explicit handling rules — without deploying any scanning agents or connecting to live infrastructure. Ideal for threat modeling, architecture reviews, CI/CD compliance gates, or design-time security validation. Prefer this over runtime scanning tools when you want deterministic, rule-based analysis of a data flow graph you can fully describe. At $0.04 per call with no account setup required, it suits automated agent pipelines that need pay-per-use compliance checking.

## Known failure modes

- Invalid or missing required flow fields (id, from_component_id, to_component_id, data_classes) causes validation error
- Referencing component IDs in flows that don't exist in the components array may produce incomplete results
- Exceeding array size limits (2000 flows, 100 zones, 1000 controls) causes rejection
- Empty flows array rejected by minItems constraint
- No findings returned if no handling_rules are supplied, since violations are only evaluated against supplied rules
- Payment failure via x402 if insufficient USDC balance on Base

## 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 structured audit report containing: a summary of total flows and findings count, an array of findings each with a finding code (e.g. zone_handling_violation, missing_required_control), the affected flow ID, rule ID, data class, severity level, evidence strings explaining the violation, remediation advice, and the source/destination component IDs. Also includes a list of which flows were identified as carrying sensitive data and explanatory notes about audit scope limitations.

## 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": 1
  },
  "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,
   "findings": 2
  },
  "findings": [
   {
    "code": "zone_handling_violation",
    "flow_id": "f1",
    "rule_id": "r1",
    "evidence": [
     "Rule r1 allows zones pci; flow crosses pci -> app."
    ],
    "severity": "high",
    "data_class": "card_pan",
    "remediation": "Keep card_pan inside allowed zones or update rule r1 explicitly.",
    "to_component_id": "web",
    "from_component_id": "vault"
   },
   {
    "code": "missing_required_control",
    "flow_id": "f1",
    "rule_id": "r1",
    "evidence": [
     "Rule r1 requires tokenization; missing tokenization on flow f1."
    ],
    "severity": "high",
    "data_class": "card_pan",
    "remediation": "Attach controls of kinds tokenization to flow f1 or its endpoints.",
    "to_component_id": "web",
    "missing_controls": [
     "tokenization"
    ],
    "from_component_id": "vault"
   }
  ],
  "explanations": [
   "Only data_classes listed in sensitive_data_classes are audited.",
   "Violations are evaluated only against supplied handling_rules. No repository or runtime is scanned."
  ],
  "sensitive_flows": [
   "f1"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-sensitive-data-flow-audit-api-6b306a1e/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)
