ToolVet
72trust / 100

Near Wallet Activity

by NEAR Wallet Activity in Onchain & crypto

x402 APIPassing, checked 7 h ago

Recent history of a NEAR account, summed up: transactions signed and received, failures, NEAR sent and received, token flows in and out per token, the contracts it calls most, who it deals with most, and signals (inactive, failing, receive-only). One-line summary plus the last 10 transactions. Reads the NearBlocks indexer; limit sets how many recent transactions (default 25).

GET
https://402.com.tr/api/x402/near-wallet-activity
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
459 ms
595 ms slowest 5%
Last check
Passed
7 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/near-wallet-activity

Each call costs $0.02 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/near-wallet-activity?account=tether.multisafe.near&limit=25

Parameters

ParameterTypeRequiredDescription
accountstringYesNEAR account
limitstringNoRecent transactions to read (optional, 5-50)

Example response

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

{
  "chain": "near",
  "checkedAt": "2026-10-11T17:19:57.548Z",
  "kind": "sub-account",
  "recentCount": 10,
  "signalsCount": 2,
  "tokenFlowsCount": 1,
  "topCallsCount": 0,
  "topCounterpartiesCount": 2
}

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

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/near-wallet-activity?account=tether.multisafe.near&limit=25'

# 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/near-wallet-activity?account=tether.multisafe.near&limit=25' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fnear-wallet-activity
const res = await pay("https://402.com.tr/api/x402/near-wallet-activity?account=tether.multisafe.near&limit=25");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
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/near-wallet-activity?account=tether.multisafe.near&limit=25")
    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
7 h agoPassed402469 ms$0.02
17 h agoPassed402405 ms$0.02
27 h agoPassed402644 ms$0.02
37 h agoPassed402369 ms$0.02
42 h agoPassed402489 ms$0.02
Show 10 older checks
46 h agoPassed402499 ms$0.02
2 days agoPassed402388 ms$0.02
2 days agoPassed402466 ms$0.02
2 days agoPassed402445 ms$0.02
3 days agoPassed402470 ms$0.02
3 days agoPassed402346 ms$0.02
3 days agoPassed402508 ms$0.02
3 days agoPassed402595 ms$0.02
3 days agoPassed402523 ms$0.02
4 days agoPassed402368 ms$0.02