Mutable-risk report for a token — can the owner still turn it hostile?
Mutable-risk report for a token — can the owner still turn it hostile? No API key, no account, no signup; pay per call in USDC on Base. GET ?address=0x... (required), chain=ethereum|base (default base). Direct on-chain reads only: eth_getCode, owner(), pendingOwner(), paused(), EIP-1967 slots. Returns mutable_risk_score, verdict, can_turn_hostile, time_to_rug, every owner power explained in plain English, and raw controls. For agents holding or about to buy a token.
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://uxus.finance/api/risk/live/pro
| Category | Market data |
|---|---|
| Provider host | uxus.finance |
| Networks | base |
| Payment schemes | exact |
| Self-reported calls, 30 days | 3 from 1 payers (the provider's figure, not ours) |
Our checks, last 30 days
We never call tools that send, buy, move money or file anything, not even without paying.
Example input (from the provider)
{
"method": "GET",
"queryParams": {
"address": "0x token contract address. Required.",
"chain": "ethereum | base. Default base."
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}