77trust / 100

Address Trust

by Address Trust in Security & trust

x402 APIPassing, checked 2 h ago

๐Ÿ†• The 'who am I dealing with?' check for agents. Reads Coinbase's ONCHAIN verification (an EAS attestation by verifications.coinbase.eth) โ€” meaning the address is tied to a KYC'd Coinbase account, the strongest sybil-resistance signal on Base โ€” plus the address's Basename. Returns a verified/named/anonymous verdict + trust score. Pair with sign-guard/spend-audit for a full pre-transaction gate. Identity is a signal, not proof of honesty.

GET
https://402.com.tr/api/x402/address-trust
Price
$0.03
per call in USDC
Uptime
100%
last 30 days
Response time
455 ms
511 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history ยท Atom feed

How to call it

GET https://402.com.tr/api/x402/address-trust

Each call costs $0.03 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://402.com.tr/api/x402/address-trust?address=0x973a31858f4d2125f48c880542da11a2796f12d6

Parameters

ParameterTypeRequiredDescription
addressstringYesAddress to check

Example response

The provider's example. We can't check it without paying.

{
  "address": "0x973A31858f4D2125f48C880542DA11a2796f12D6",
  "basename": null,
  "checkedAt": "2026-10-11T17:12:32.079Z",
  "coinbaseVerified": true,
  "signalsCount": 1,
  "trustScore": 70,
  "verdict": "verified"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.03.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://402.com.tr/api/x402/address-trust?address=0x973a31858f4d2125f48c880542da11a2796f12d6'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://402.com.tr/api/x402/address-trust?address=0x973a31858f4d2125f48c880542da11a2796f12d6' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Faddress-trust
const res = await pay("https://402.com.tr/api/x402/address-trust?address=0x973a31858f4d2125f48c880542da11a2796f12d6");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://402.com.tr/api/x402/address-trust?address=0x973a31858f4d2125f48c880542da11a2796f12d6")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402446 ms$0.03
7 h agoPassed402456 ms$0.03
11 h agoPassed402476 ms$0.03
14 h agoPassed402382 ms$0.03
18 h agoPassed402481 ms$0.03
Show 10 older checks
22 h agoPassed402484 ms$0.03
26 h agoPassed402352 ms$0.03
30 h agoPassed402631 ms$0.03
34 h agoPassed402509 ms$0.03
37 h agoPassed402511 ms$0.03
41 h agoPassed402350 ms$0.03
44 h agoPassed402363 ms$0.03
2 days agoPassed402347 ms$0.03
2 days agoPassed402510 ms$0.03
2 days agoPassed402455 ms$0.03