# Bitfence Contextual Token Risk Assessment

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

Performs position-aware (contextual) risk assessment on cryptocurrency tokens, returning a risk score, risk level, and recommendation.

## Facts

- Endpoint: POST https://api.bitfence.ai/v1/risk/contextual
- Price: $0.005000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-bitfence-ai-e80a4b01
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kn3rW6ph5uwtGuPPm803K

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-e80a4b01 -d '<json body>'
```

Example prompt: Can you run a contextual risk assessment on the token I'm currently holding and tell me the risk score, risk level, and whether I should hold or exit my position?

## When to prefer this

Use this endpoint when you need position-aware, contextual token risk scoring — not just generic token metadata — especially when the user's current holdings or trade position should influence the risk assessment. Prefer over generic token info APIs when a nuanced risk_level and actionable recommendation are required.

## Known failure modes

- Missing required 'input' field returns a validation error
- Invalid or unsupported method value returns a schema error
- Unpayable or insufficient USDC balance results in x402 payment failure
- Token not recognized or unsupported returns empty or error response
- Network/service downtime returns 5xx errors

## How this service works

bitfence contextual (position-aware) token risk assessment

## Output

Returns a numeric risk_score, a categorical risk_level (e.g. low/medium/high), and a plain-language recommendation about the token given the user's position context.

## 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": [
      "POST"
     ],
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "risk_score",
      "risk_level",
      "recommendation"
     ],
     "properties": {
      "risk_level": {
       "type": "string"
      },
      "risk_score": {
       "type": "number"
      },
      "recommendation": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-bitfence-ai-e80a4b01/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)