trust-agent.io

https://trust-agent.io/v1/verify/deep

Shares a payout wallet with 6 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

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.

59
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

100.0% avg
0% 50% 100% Jul 29Aug 6Aug 13Aug 21

Response time

p50 19ms · p95 32ms
0ms 50ms 100ms Jul 29Aug 6Aug 13Aug 21
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
7/29/2026, 12:00:00 AM 100% 1 21ms
7/30/2026, 12:00:00 AM 100% 1 16ms
7/31/2026, 12:00:00 AM 100% 1 14ms
8/1/2026, 12:00:00 AM 100% 1 31ms
8/2/2026, 12:00:00 AM 100% 1 24ms
8/3/2026, 12:00:00 AM 100% 1 19ms
8/4/2026, 12:00:00 AM 100% 1 20ms
8/5/2026, 12:00:00 AM 100% 1 24ms
8/6/2026, 12:00:00 AM 100% 1 54ms
8/7/2026, 12:00:00 AM 100% 1 29ms
8/8/2026, 12:00:00 AM 100% 1 15ms
8/9/2026, 12:00:00 AM 100% 1 18ms
8/10/2026, 12:00:00 AM 100% 1 23ms
8/11/2026, 12:00:00 AM 100% 1 17ms
8/12/2026, 12:00:00 AM 100% 1 16ms
8/13/2026, 12:00:00 AM 100% 1 33ms
8/14/2026, 12:00:00 AM 100% 1 22ms
8/15/2026, 12:00:00 AM 100% 1 24ms
8/16/2026, 12:00:00 AM 100% 1 19ms
8/17/2026, 12:00:00 AM 100% 1 21ms
8/18/2026, 12:00:00 AM 100% 1 20ms
8/19/2026, 12:00:00 AM 100% 20 22ms
8/20/2026, 12:00:00 AM 100% 21 17ms
8/21/2026, 12:00:00 AM 100% 4 25ms
59
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
55

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
1

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
Registrar
Domain registered
Hosting network
Hosting country

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

15
payments (30d)
0.08
USD volume (30d)
2
paying wallets (30d)

Payments per day

last payment 8/16/2026
0 3 6 Jul 27Jul 28Aug 14Aug 16
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
7/27/2026 1 0 1
7/28/2026 6 0.03 1
7/29/2026 4 0.02 1
8/14/2026 1 0 1
8/16/2026 3 0.02 1

This payout wallet is shared: figures cover all 7 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

Response schema
{
  "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 — 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"
}