# BRAINIAC Token Security Risk Verdict

> BRAINIAC Token Security Risk Verdict is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.05/call, status unknown (last checked 2026-11-17).

Analyzes an ERC-20 token contract address on Base and returns a structured security risk verdict with findings, signals, and an assessment.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/token-security/risk-verdict?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-token-security-risk-verdict-e000f7a2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lD9ZBffJIHi6Qbyt5Mz3e

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-token-security-risk-verdict-e000f7a2 -d '<json body>'
```

Example prompt: Can you run a security risk check on the token at address 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 on Base and tell me if there are any blacklist or honeypot signals in its bytecode?

## When to prefer this

Use this endpoint when an AI agent needs a fast, structured, pay-per-call security verdict on a specific ERC-20 token contract on Base before executing a swap, adding to a portfolio, or recommending it to a user. It is best suited for lightweight pre-trade due diligence where bytecode-level signal detection (e.g. blacklist selectors) matters, and where no account setup or API key is desired. Prefer this over full smart contract audit services when you need a quick programmatic verdict rather than a human-readable audit report.

## Known failure modes

- Invalid token address format returns a validation error
- Token address with no deployed code may return a fact finding of no contract code
- Simulation not performed so sell-side honeypot not detected (unavailable finding)
- Network connectivity issues to Base JSON-RPC may cause retrieval failure
- Payment not completed via x402 results in 402 response with no data
- False negatives possible — absence of signals does not confirm token safety

## How this service works

Read a Base token contract and return an evidence-based verdict. Facts, signals, and unavailable checks are separate. No risk score is produced, and absence of a signal is not a safety approval.

## Output

A JSON object containing: the chain ID (8453 for Base), the data sources used (e.g. Base JSON-RPC), a list of findings each with a code, kind (fact/signal/unavailable), detail text, and evidence, an overall assessment string (e.g. 'signals_present'), a list of limitations, timestamps, the queried token address, and an 'approvesInteraction' boolean indicating whether the service vouches for safe interaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tokenAddress": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "partial",
  "chainId": 8453,
  "sources": [
   {
    "url": "https://mainnet.base.org",
    "source": "Base JSON-RPC",
    "retrievedAt": "2026-11-02T18:00:00.000Z"
   }
  ],
  "findings": [
   {
    "code": "contract_code_present",
    "kind": "fact",
    "detail": "The address has runtime code at the latest block.",
    "evidence": "2456"
   },
   {
    "code": "selector_fe575a87",
    "kind": "signal",
    "detail": "Runtime bytecode contains the 4-byte selector for isBlacklisted(address). Presence in bytecode does not prove the funct…",
    "evidence": "fe575a87"
   },
   "…"
  ],
  "result_id": "a1b2c3d4e5f60718293a4b5c6d7e8f90",
  "assessment": "signals_present",
  "limitations": [
   "Absence of a signal is not evidence that the token is safe, and this response does not approve interacting with it.",
   "status=partial keeps successful evidence and lists only the timed-out check in missing_items. A reused Idempotency-Key …",
   "…"
  ],
  "received_at": "2026-11-02T18:00:01.000Z",
  "retrievedAt": "2026-11-02T18:00:00.000Z",
  "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "missing_items": [
   {
    "check": "paused_read_timeout",
    "detail": "eth_call for paused() timed out. Bytecode facts above still stand.",
    "reason": "timeout"
   }
  ],
  "approvesInteraction": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-token-security-risk-verdict-e000f7a2/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)
