10trust / 100

Wallet

by Base Wallet Profile in Onchain & crypto

x402 APIFailing, checked 10 h ago

Get an on-chain activity profile and activity score for an EVM address on Base.

GET
https://vladboyarinov-x402-api.onrender.com/wallet/:address
Price
$0.01
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
10 h ago, next in 3 days

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 10 h ago: Expected HTTP 402, got 404

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://vladboyarinov-x402-api.onrender.com/wallet/:address

Each call costs $0.01 in USDC on Base Sepolia, 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://vladboyarinov-x402-api.onrender.com/wallet/:address

Example response

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

{
  "activityScore": 0,
  "address": "0x0000000000000000000000000000000000000001",
  "ageDays": null,
  "balanceEth": "0.0",
  "chain": "base",
  "dataSources": [
    "base_rpc",
    "blockscout"
  ],
  "firstSeen": null,
  "generatedAt": "2026-01-01T00:00:00.000Z",
  "isContract": false,
  "label": null,
  "lastSeen": null,
  "outgoingTxCount": 0,
  "riskFlags": [
    "no_activity",
    "low_balance"
  ],
  "tokenTransfers": 0,
  "totalTxCount": 0,
  "verdict": "empty"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://vladboyarinov-x402-api.onrender.com/wallet/:address'

# 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://vladboyarinov-x402-api.onrender.com/wallet/:address' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fvladboyarinov-x402-api.onrender.com%2Fwallet%2F%3Aaddress
const res = await pay("https://vladboyarinov-x402-api.onrender.com/wallet/:address");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://vladboyarinov-x402-api.onrender.com/wallet/:address")
    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
10 h agoExpected HTTP 402, got 404404231 ms-
4 days agoExpected HTTP 402, got 404404253 ms-
4 days agoExpected HTTP 402, got 404404246 ms-
4 days agoExpected HTTP 402, got 404404233 ms-
4 days agoExpected HTTP 402, got 404404595 ms-
Show 10 older checks
4 days agoExpected HTTP 402, got 404404246 ms-
5 days agoExpected HTTP 402, got 404404305 ms-
5 days agoExpected HTTP 402, got 404404222 ms-
5 days agoExpected HTTP 402, got 404404558 ms-
5 days agoExpected HTTP 402, got 404404293 ms-
5 days agoExpected HTTP 402, got 404404244 ms-
5 days agoExpected HTTP 402, got 404404241 ms-
6 days agoExpected HTTP 402, got 404404294 ms-
6 days agoExpected HTTP 402, got 404404241 ms-
6 days agoExpected HTTP 402, got 404404297 ms-