trust-agent.io

https://trust-agent.io/v1/endpoint/screen

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

Is this x402 endpoint safe to pay? Reads its payment challenge under BOTH protocol versions — v1 body and v2 PAYMENT-REQUIRED header, so a v2-only service is not read as dead — then screens the payout wallet it advertises: OFAC sanctions, sybil-filtered ERC-8004 reputation, on-chain behaviour. Flags versions that name different recipients. Scores the wallet, not the service. Free alternative: GET /v1/endpoint. Trial: 3 free calls/wallet/24h — https://trust-agent.io/v1/trial.

61
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% Mon 8 PMThu 1 AMSat 4 AMMon 6 PM

Response time

p50 20ms · p95 111ms
0ms 100ms 200ms Mon 8 PMThu 1 AMSat 4 AMMon 6 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/28/2026, 8:00:00 PM 100% 1 21ms
9/28/2026, 10:00:00 PM 100% 1 17ms
9/29/2026, 12:00:00 AM 100% 1 16ms
9/29/2026, 1:00:00 AM 100% 1 17ms
9/29/2026, 3:00:00 AM 100% 1 16ms
9/29/2026, 5:00:00 AM 100% 1 16ms
9/29/2026, 7:00:00 AM 100% 1 16ms
9/29/2026, 9:00:00 AM 100% 1 16ms
9/29/2026, 11:00:00 AM 100% 1 22ms
9/29/2026, 1:00:00 PM 100% 1 16ms
9/29/2026, 2:00:00 PM 100% 1 29ms
9/29/2026, 4:00:00 PM 100% 1 27ms
9/29/2026, 7:00:00 PM 100% 1 21ms
9/29/2026, 9:00:00 PM 100% 1 18ms
9/29/2026, 11:00:00 PM 100% 1 19ms
9/30/2026, 1:00:00 AM 100% 1 19ms
9/30/2026, 3:00:00 AM 100% 1 25ms
9/30/2026, 5:00:00 AM 100% 1 16ms
9/30/2026, 7:00:00 AM 100% 1 16ms
9/30/2026, 9:00:00 AM 100% 1 17ms
9/30/2026, 11:00:00 AM 100% 1 17ms
9/30/2026, 1:00:00 PM 100% 1 40ms
9/30/2026, 3:00:00 PM 100% 1 20ms
9/30/2026, 5:00:00 PM 100% 1 23ms
9/30/2026, 7:00:00 PM 100% 1 26ms
9/30/2026, 9:00:00 PM 100% 1 16ms
9/30/2026, 11:00:00 PM 100% 1 18ms
10/1/2026, 1:00:00 AM 100% 1 16ms
10/1/2026, 3:00:00 AM 100% 1 17ms
10/1/2026, 5:00:00 AM 100% 1 20ms
10/1/2026, 7:00:00 AM 100% 1 19ms
10/1/2026, 9:00:00 AM 100% 1 19ms
10/1/2026, 11:00:00 AM 100% 1 22ms
10/1/2026, 1:00:00 PM 100% 1 18ms
10/1/2026, 3:00:00 PM 100% 1 16ms
10/1/2026, 5:00:00 PM 100% 1 20ms
10/1/2026, 7:00:00 PM 100% 1 17ms
10/1/2026, 9:00:00 PM 100% 1 16ms
10/1/2026, 11:00:00 PM 100% 1 17ms
10/2/2026, 1:00:00 AM 100% 1 19ms
10/2/2026, 3:00:00 AM 100% 1 19ms
10/2/2026, 5:00:00 AM 100% 1 15ms
10/2/2026, 7:00:00 AM 100% 1 26ms
10/2/2026, 9:00:00 AM 100% 1 16ms
10/2/2026, 11:00:00 AM 100% 1 20ms
10/2/2026, 1:00:00 PM 100% 1 18ms
10/2/2026, 3:00:00 PM 100% 1 21ms
10/2/2026, 5:00:00 PM 100% 1 19ms
10/2/2026, 7:00:00 PM 100% 1 18ms
10/2/2026, 9:00:00 PM 100% 1 25ms
10/2/2026, 11:00:00 PM 100% 1 17ms
10/3/2026, 12:00:00 AM 100% 1 16ms
10/3/2026, 2:00:00 AM 100% 1 18ms
10/3/2026, 4:00:00 AM 100% 1 30ms
10/3/2026, 6:00:00 AM 100% 1 15ms
10/3/2026, 8:00:00 AM 100% 1 20ms
10/3/2026, 10:00:00 AM 100% 1 16ms
10/3/2026, 12:00:00 PM 100% 1 17ms
10/3/2026, 2:00:00 PM 100% 1 24ms
10/3/2026, 4:00:00 PM 100% 1 27ms
10/3/2026, 6:00:00 PM 100% 1 111ms
10/3/2026, 8:00:00 PM 100% 1 108ms
10/3/2026, 11:00:00 PM 100% 1 119ms
10/4/2026, 1:00:00 AM 100% 1 103ms
10/4/2026, 2:00:00 AM 100% 1 118ms
10/4/2026, 4:00:00 AM 100% 1 107ms
10/4/2026, 6:00:00 AM 100% 1 93ms
10/4/2026, 8:00:00 AM 100% 1 104ms
10/4/2026, 1:00:00 PM 100% 1 128ms
10/4/2026, 3:00:00 PM 100% 1 33ms
10/4/2026, 4:00:00 PM 100% 1 91ms
10/4/2026, 6:00:00 PM 100% 1 106ms
10/4/2026, 8:00:00 PM 100% 1 115ms
10/5/2026, 2:00:00 AM 100% 1 90ms
10/5/2026, 7:00:00 AM 100% 1 87ms
10/5/2026, 9:00:00 AM 100% 1 100ms
10/5/2026, 11:00:00 AM 100% 1 93ms
10/5/2026, 1:00:00 PM 100% 1 98ms
10/5/2026, 2:00:00 PM 100% 1 96ms
10/5/2026, 4:00:00 PM 100% 1 69ms
10/5/2026, 6:00:00 PM 100% 1 71ms
61
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
61

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

Activity
3

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
RS-1125
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)

37
payments (30d)
0.19
USD volume (30d)
5
paying wallets (30d)

Payments per day

last payment 10/5/2026
0 5 9 Sep 13Sep 29Oct 2Oct 5
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/13/2026 9 0.05 1
9/14/2026 1 0 1
9/28/2026 2 0 2
9/29/2026 9 0.06 2
9/30/2026 1 0.01 1
10/1/2026 8 0.03 2
10/2/2026 1 0 1
10/3/2026 3 0.01 1
10/4/2026 2 0.02 1
10/5/2026 1 0.01 1

This payout wallet is shared: figures cover all 11 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": {
    "additionalPayoutWallets": {
      "description": "present only when the offers disagree about the recipient"
    },
    "components": {
      "description": "per-rule scoring breakdown"
    },
    "flags": {
      "description": "array of {code, severity, title, detail}"
    },
    "offers": {
      "description": "every advertised offer: payTo, network, asset, amount, version"
    },
    "payoutWallet": {
      "description": "the address scored"
    },
    "paywalled": {
      "description": "whether the endpoint answered 402 with a parseable payment offer"
    },
    "recommendation": {
      "description": "proceed | proceed_with_caution | hold | block | insufficient_data"
    },
    "trustScore": {
      "description": "0-100 for the payout wallet; null when no rule could be evaluated"
    },
    "x402Versions": {
      "description": "which protocol generations answered — [1], [2] or [1,2]"
    }
  },
  "type": "object"
}