Should you approve this contract?
Should you approve this contract? Everything in quick, plus static analysis of the bytecode: privileged functions (mint, pause, blacklist, arbitrary withdrawal), proxy and upgradeability detection, dangerous opcodes, DeFi protocol classification and source-verification status.
Not tested: has real-world effectsour last check, 2026-09-24
0 of 0checks answered this week
n/amedian answer time
$0.01listed price per call
n/aprice it asked us
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://trust-agent.io/v1/verify/deep
| Category | Market data |
|---|---|
| Provider host | trust-agent.io |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 1 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": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"chain": "base",
"type": "contract"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"properties": {
"address": {
"description": "REQUIRED. Contract address to analyse.",
"type": "string"
},
"chain": {
"description": "OPTIONAL. Only \"base\" is served; any other value is refused rather than answered from the wrong chain. Defaults to base.",
"type": "string"
},
"type": {
"description": "OPTIONAL. contract | defi_protocol.",
"type": "string"
}
},
"required": [
"address"
],
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"properties": {
"components": {
"description": "per-rule scoring breakdown; the score is reconstructable from these plus overrides"
},
"confidence": {
"description": "0-1, how much evidence backs the score"
},
"contract": {
"description": "bytecode analysis: opcodes, proxy kind, privileged functions, interfaces, protocol class, safetyScore"
},
"flags": {
"description": "includes contract-specific findings"
},
"overrides": {
"description": "hard caps applied after weighting, each with from/cap/reason"
},
"recommendation": {
"description": "proceed | proceed_with_caution | hold | block | insufficient_data. insufficient_data means no judgment was possible \u2014 treat it as unknown, not as risky."
},
"riskBand": {
"description": "minimal | low | moderate | elevated | severe | unknown"
},
"trustScore": {
"description": "0-100, higher is safer; null when no rule could be evaluated"
}
},
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}