Bitfence
Skill by bilsbys
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bilsbys/bitfenceBitfence — pre-transaction risk infrastructure for AI agents operating on-chain
Bitfence is an optional, user-controlled pre-transaction risk-scoring service for tokens on Solana and Base. When the user is about to interact with an unfamiliar token, this skill lets you fetch a risk assessment from the public Bitfence API so the user can make an informed decision.
Bitfence is read-only. It does not sign transactions, broadcast transactions, hold funds, or interact with the user's wallet. It returns a JSON risk report and nothing more.
This skill provides advisory guardrails. The user is always the final authority. If the user explicitly chooses to proceed after seeing a risk warning, that is their decision and you should respect it.
Privacy and data sent
Bitfence only ever receives public on-chain identifiers. Specifically:
- Token risk endpoint (
GET /v1/risk/{chain}/{token_address}) — sends only the chain name and the public token contract address. No wallet address, no portfolio, no transaction details. - Contextual endpoint (
POST /v1/risk/contextual) — additionally sends the position size and total portfolio size in USD, only when the user has explicitly opted in to contextual analysis. No wallet address is ever transmitted.
Do not call the contextual endpoint without the user's awareness that position-size context will be shared with the API.
Cost transparency
Bitfence is monetised via the x402 protocol — each scoring request costs a small amount of USDC on Base mainnet (typically a few tenths of a cent). Before you begin using Bitfence in a session:
- Inform the user that risk checks are paid and will draw from the wallet's USDC balance on Base mainnet.
- Ask for the user's consent the first time you call Bitfence in a session, or when the user has not previously authorised paid risk checks.
- Do not call Bitfence repeatedly in tight loops, batch operations, or polling patterns. Use it once per distinct trade decision.
- If the user declines paid checks, fall back to whatever native safety checks you and the user have agreed on.
If x402 payment fails, do not retry blindly. Inform the user that the wallet needs USDC on Base mainnet to use Bitfence, and let the user decide whether to top up or skip the check.
Available endpoints
Base URL: https://api.bitfence.ai
| Method | Path | Purpose | Paid? |
|---|---|---|---|
GET | / | Service metadata — name, version, status. | Free |
GET | /health | Health probe. Returns 200 OK when operational. | Free |
GET | /v1/risk/{chain}/{token_address} | Token risk assessment. chain is solana or base. | Yes (x402) |
POST | /v1/risk/contextual | Position-aware risk assessment with slippage, MEV exposure, and a suggested position cap. | Yes (x402) |
When Bitfence is useful
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bilsbys-bitfence": {
"enabled": true,
"auto_update": true
}
}
}