ToolVet
77trust / 100

Address Label

by 402.com.tr in Onchain & crypto

x402 APIPassing, checked 3 h ago

What is this Base address? Matches a sourced registry of known protocol, exchange, bridge, locker and burn addresses (each with the docs/deployments/Basescan source it came from), then reads the chain: contract vs EOA (EIP-7702 delegation shown), ERC-4626 vault (asset()), Safe multisig (getThreshold), DEX pool interface (token0/token1). Unmatched addresses are reported as unlabelled, never guessed.

GET
https://402.com.tr/api/x402/address-label
Price
$0.005
per call in USDC
Uptime
100%
last 30 days
Response time
518 ms
700 ms slowest 5%
Last check
Passed
3 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 · Watch with other listings

How to call it

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

Each call costs $0.005 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-label?address=0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb

Parameters

ParameterTypeRequiredDescription
addressstringYesBase address to identify

Example response

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

{
  "address": "0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb",
  "checkedAt": "2026-10-15T03:00:50.121Z",
  "detectedCount": 0,
  "erc4626": null,
  "isContract": true,
  "kind": "lending",
  "pool": null,
  "safe": null
}

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.005.

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-label?address=0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb'

# 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-label?address=0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb' \
  | 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Faddress-label
const res = await pay("https://402.com.tr/api/x402/address-label?address=0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb");
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
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-label?address=0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb")
    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
3 h agoPassed402465 ms$0.005
8 h agoPassed402564 ms$0.005
13 h agoPassed402389 ms$0.005
17 h agoPassed402609 ms$0.005
22 h agoPassed402700 ms$0.005
Show 3 older checks
26 h agoPassed402518 ms$0.005
30 h agoPassed402501 ms$0.005
40 h agoPassed402584 ms$0.005