Six chains, one risk contract
Four new chains. Token risk assessments are now live on six chains: Solana, Base, Ethereum, Arbitrum, BSC, and HyperEVM. Same endpoints, same response shape everywhere — swap the chain identifier in the path and nothing else about your integration changes:
curl https://api.bitfence.ai/v1/risk/hyperevm/0x5555555555555555555555555555555555555555No chain shipped on trust. Every chain goes through a live-token release gate that measures its safety-critical data legs against real tokens before it is enabled — a chain that cannot prove its checks does not go live.
Categories are loss mechanisms now. The engine scores six categories, and each one is a distinct way a holder's position gets destroyed: exit integrity, supply integrity, liquidity integrity, holder and insider risk, provenance, and market integrity. A category is never a data source and never an analysis technique — which means sources and techniques can improve underneath without the meaning of a score changing.
The engine grades its own evidence. Every fact feeding a safety check is known-true, known-false, or unknown — and unknown is never quietly converted into a known. Missing data cannot fire a circuit breaker, and it cannot suppress one. When a safety-critical check cannot run, the response says so by name and the recommendation is capped at REQUIRE_HUMAN_APPROVAL. When independent sources disagree on a fact, the fact is marked contested, named in the response, and excluded from the confidence value — disagreement is surfaced, never averaged away.
Two classes of circuit breakers. Measured threats — a sell that demonstrably reverts in simulation, a confiscatory sell tax — override everything, including trusted-token status. Heuristic flags floor the score for unknown tokens but never override the curated trusted-token registry, because the same configuration that is a trap in a day-old token is documented design in a major stablecoin.
Billing follows delivery. A paid request settles only when the assessment is actually delivered. A request that fails — including a query to a chain that is switched off — is never charged.