$0.01
per call · USD Coin on Base
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.
Endpoint
GET https://trust-agent.io/v1/verify/deep1
Calls / 30d
1
Unique payers / 30d
Sep 3
Last called
exact
Payment scheme
Call this service
import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const fetchWithPay = wrapFetchWithPayment(fetch, account);
const res = await fetchWithPay("https://trust-agent.io/v1/verify/deep", {
method: "GET",
});
const data = await res.json();curl -X GET \
"https://trust-agent.io/v1/verify/deep?address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&chain=base&type=contract" \
-H "X-PAYMENT: <signed x402 payment>"Example response
{
"components": "per-rule scoring breakdown; the score is reconstructable from these plus overrides",
"confidence": "0-1, how much evidence backs the score",
"contract": "bytecode analysis: opcodes, proxy kind, privileged functions, interfaces, protocol class, safetyScore",
"flags": "includes contract-specific findings",
"overrides": "hard caps applied after weighting, each with from/cap/reason",
"recommendation": "proceed | proceed_with_caution | hold | block | insufficient_data. insufficient_data means no judgment was possible — treat it as unknown, not as risky.",
"riskBand": "minimal | low | moderate | elevated | severe | unknown",
"trustScore": "0-100, higher is safer; null when no rule could be evaluated"
}Payment details
0x6121654d3fd4c8b42a90d30472e4d40927c3e6bbUSD Coin · 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913Is this your API?
Pin it to the top of Other and the homepage with a featured placement.
More from TrustAgent & similar services
TrustAgent · Registry Agents
trust-agent.io
The filtered ERC-8004 directory: which registered agents are actually alive, and which accept x402. Roughly 15% of registrations on Base have both a compliant registration file and a declared service — this returns those, rather than making you screen sixty thousand addresses one at a time to find them. 100 agents per page.
TrustAgent · Endpoint Screen
trust-agent.io
Is this x402 endpoint safe to pay? Reads the endpoint's own payment challenge under BOTH protocol versions — v1 body and v2 PAYMENT-REQUIRED header, so a live v2-only service is not reported as dead — extracts the payout wallet it advertises, and screens that wallet: OFAC sanctions, sybil-filtered ERC-8004 reputation, on-chain behaviour. Flags an endpoint that names different recipients under the two versions. Scores the wallet, not the service behind it, and says so.
TrustAgent · Search Agents
trust-agent.io
Which live agents can do X? Searches what ERC-8004 agents DECLARE about themselves — skills, domains, name — across the registrations this service fetches on a rolling sweep, and returns only the ones actually answering. Each row carries the service endpoint to call and the wallet a payment would go to. Roughly 8% of registrations on Base are live at all; the alternative is fetching sixty thousand files yourself.