Crypto Wallet Report
by ISHOB in Onchain & crypto
Wallet risk & activity report in one call — vet a counterparty before you transact: the address's own reputation (sanctions, phishing, theft, laundering, mixer... Powered by GoPlus Security), open token approvals with risky spenders, scam tokens held, and the full portfolio with USD values across Ethereum, Base, Arbitrum, Optimism, Polygon and BNB Chain (or Solana: holdings only). Verdict: clean / caution / high-risk / flagged / incomplete, with every reason listed.
https://api.ishob.com/v1/crypto/wallet-report- Price
- $0.03
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 778 ms
- 1.2 s slowest 5%
- Last check
- Passed
- 2 min ago, next in 26 min
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.ishob.com/v1/crypto/wallet-report
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://api.ishob.com/v1/crypto/wallet-report?address=0x098b716b8aaf21512996dc57eb0615e2383e2f96Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | EVM 0x address or Solana base58 address |
chains | string | No | EVM only: comma-separated subset of ethereum, base, arbitrum, optimism, polygon, bsc (default all) |
Example response
The provider's example. We can't check it without paying.
{
"approvals": {
"open": 0,
"risky": 0
},
"holdings": {
"total_value_usd": 261390
},
"reputation": {
"flags": [
"on a sanctions list",
"stealing attacks"
]
},
"summary": "FLAGGED: Address flagged: on a sanctions list · portfolio $261,390",
"verdict": "flagged"
}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://api.ishob.com/v1/crypto/wallet-report?address=0x098b716b8aaf21512996dc57eb0615e2383e2f96'
# 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://api.ishob.com/v1/crypto/wallet-report?address=0x098b716b8aaf21512996dc57eb0615e2383e2f96' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Fapi.ishob.com%2Fv1%2Fcrypto%2Fwallet-report
const res = await pay("https://api.ishob.com/v1/crypto/wallet-report?address=0x098b716b8aaf21512996dc57eb0615e2383e2f96");
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://api.ishob.com/v1/crypto/wallet-report?address=0x098b716b8aaf21512996dc57eb0615e2383e2f96")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 min ago | Passed | 402 | 130 ms | $0.03 |
| 4 h ago | Passed | 402 | 714 ms | $0.03 |
| 8 h ago | Passed | 402 | 778 ms | $0.03 |
| 13 h ago | Passed | 402 | 1.1 s | $0.03 |
| 17 h ago | Passed | 402 | 887 ms | $0.03 |
Show 7 older checks
| 21 h ago | Passed | 402 | 1.0 s | $0.03 |
| 25 h ago | Passed | 402 | 633 ms | $0.03 |
| 30 h ago | Passed | 402 | 179 ms | $0.03 |
| 34 h ago | Passed | 402 | 1.2 s | $0.03 |
| 38 h ago | Passed | 402 | 903 ms | $0.03 |
| 42 h ago | Passed | 402 | 825 ms | $0.03 |
| 2 days ago | Passed | 402 | 37 ms | $0.03 |