# BRAINIAC Crypto Intent Safety Analyzer

> BRAINIAC Crypto Intent Safety Analyzer 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-13).

Analyzes EVM transaction calldata or EIP-712 typed data to score intent safety and detect unintended token transfer risks

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/crypto-security/intent-safety?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-crypto-intent-safety-analyzer-16492b5a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_plof6k2NJfA6EhxP76xaf

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-crypto-intent-safety-analyzer-16492b5a -d '<json body>'
```

Example prompt: Before I sign this transaction, can you analyze its calldata — 0x095ea7b30000000000000000000000002222222222222222222222222222222222222222ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff — and tell me the intent safety score, what it actually does in plain English, and whether there's any risk of unintended token transfers?

## When to prefer this

Use this endpoint when an AI agent or wallet needs to validate the safety of an EVM transaction or EIP-712 signing request before execution — especially for token approvals, permit signatures, or any raw calldata that could result in token loss. Preferred over generic contract decoders when you need both a human-readable explanation AND a quantified risk score for unintended transfers in a single pay-per-call, no-account-required API call via x402.

## Known failure modes

- Invalid or malformed calldata hex returns a parsing error
- Transaction data field missing or empty causes validation failure
- EIP-712 typed data missing required primaryType or message fields returns schema error
- Ambiguous or unknown contract ABI may produce a low-confidence or generic intent description
- Payment of 0.04 USDC via x402 on Base must succeed before the endpoint responds

## How this service works

Read a caller-supplied EVM transaction or an EIP-712 typed-data message and describe the transfer, approval, permit, or outer call it encodes. Known selectors are transfer, transferFrom, approve, increaseAllowance, setApprovalForAll, permit, multicall, aggregate, and execute. The score is a local penalty count. It does not simulate the call or read a chain.

## Output

Returns an intent_safety_score (0-100, higher is safer), a human_readable_intent string explaining in plain English what the transaction or typed data will do onchain, and an unintended_transfers_risk score (0-100, higher means more risk of unintended token movements).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "typed_data": {
   "type": "object",
   "required": [
    "primaryType",
    "message"
   ],
   "properties": {
    "types": {
     "type": "object",
     "propertyNames": {
      "type": "string"
     },
     "additionalProperties": {
      "type": "array",
      "items": {
       "type": "object",
       "required": [
        "name",
        "type"
       ],
       "properties": {
        "name": {
         "type": "string",
         "maxLength": 80,
         "minLength": 1
        },
        "type": {
         "type": "string",
         "maxLength": 80,
         "minLength": 1
        }
       },
       "additionalProperties": false
      },
      "maxItems": 40
     }
    },
    "domain": {
     "type": "object",
     "propertyNames": {
      "type": "string"
     },
     "additionalProperties": {}
    },
    "message": {
     "type": "object",
     "propertyNames": {
      "type": "string"
     },
     "additionalProperties": {}
    },
    "primaryType": {
     "type": "string",
     "maxLength": 80,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "transaction": {
   "type": "object",
   "required": [
    "data"
   ],
   "properties": {
    "to": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$"
    },
    "data": {
     "type": "string",
     "pattern": "^(0x)?[0-9a-fA-F]*$",
     "maxLength": 100000
    },
    "value": {
     "type": "string",
     "pattern": "^(0x[0-9a-fA-F]+|\\d+)$"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "partial",
  "result_id": "a1b2c3d4e5f60718293a4b5c6d7e8f90",
  "received_at": "2026-11-12T12:00:00.000Z",
  "missing_items": [
   {
    "check": "chain_state_not_read",
    "detail": "No chain state was read. This response is local static analysis only.",
    "reason": "not_supported"
   }
  ],
  "intent_safety_score": 55,
  "human_readable_intent": "Approve 0x2222222222222222222222222222222222222222 to spend the maximum uint256 of the token at 0x833589fcd6edb6e08f4c7…",
  "unintended_transfers_risk": 55
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-crypto-intent-safety-analyzer-16492b5a/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)
