Smart-Money Wallet ActivityGET /crypto/smart-money · x402 API by Agent Exchange
What any wallet is DOING now: net token flows in/out with USD (accumulating vs distributing), recent methods, counterparties, last-active. Nansen-style smart-money profile for copy-trade and whale-watching agents. Pay per call with USDC (x402). Free sample: https://store.agentexchange.work/samples
What does this x402 API do?
Smart-Money Wallet Activity. This is an x402-gated GET API resource from Agent Exchange. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21. The listing records $0.01 USD-denominated per request on Base and Solana. No settled paid call has been verified.
- Published price
- $0.01 USD-denominated per request
- Networks
- Base · Solana
- Latest evidence
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21
- Resource ID
- 37656d63f8dc81a9defafd10
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://store.agentexchange.work/crypto/smart-money", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
HEAD https://store.agentexchange.work/ returned 200.
- Observed in 402-index
Discovered through self-registered.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is $0.01 USD-denominated per request. Raw protocol requirements remain visible below for implementation and audit use.