# Bitfence Token Risk Assessment API

> Bitfence Token Risk Assessment API is a paid API for AI agents from api.bitfence.ai, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-13).

Assesses the risk profile of a cryptocurrency token by analyzing on-chain and contextual signals and returning a risk score or classification.

## Facts

- Endpoint: GET https://api.bitfence.ai/v1/risk
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-bitfence-ai-f9d02910
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tBAIqdki0kmWWxKcjVSH9

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 api-bitfence-ai-f9d02910
```

Example prompt: Before I swap into this token, can you check the Bitfence risk score for contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum and tell me if it's flagged as high risk?

## When to prefer this

Use this endpoint when you need a fast, per-token risk score for a specific contract address before executing a trade, listing a token, or routing a DeFi transaction. Prefer this over the contextual (position-aware) sibling endpoint when you do not need portfolio-position context and just want a standalone token risk verdict.

## Known failure modes

- Invalid or unrecognized token address returns error
- Unsupported blockchain network returns error
- Malformed request body returns 400-level error
- Token has insufficient on-chain history for scoring
- Payment not included or insufficient USDC balance causes 402 error
- Rate limiting if too many requests are made

## How this service works

bitfence token risk assessment

## Output

A risk assessment response including a risk score, risk level classification (e.g. low/medium/high), and contributing risk signals or threat indicators for the queried token.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "risk_score",
      "risk_level",
      "confidence",
      "recommendation"
     ],
     "properties": {
      "chain": {
       "type": "string"
      },
      "confidence": {
       "type": "number"
      },
      "risk_level": {
       "enum": [
        "LOW",
        "MEDIUM",
        "HIGH"
       ],
       "type": "string"
      },
      "risk_score": {
       "type": "number"
      },
      "token_address": {
       "type": "string"
      },
      "recommendation": {
       "enum": [
        "PROCEED",
        "REQUIRE_HUMAN_APPROVAL",
        "BLOCK"
       ],
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-bitfence-ai-f9d02910/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.bitfence.ai](https://www.zero.xyz/host/api.bitfence.ai/llms.txt)