Funding and cross-chain

Two ways to follow money into and out of a wallet: back up its funding chain, and across bridges to other chains.

3 routes. Every path below is served under https://api.scanner.net, and every request carries the key header, so those two are not repeated per route. Shared errors, limits and streaming are in Requests and errors.

Funding chain stream

GET /funding-chain/stream

Walks a wallet's funding back one hop at a time: who funded it, who funded that wallet, and so on, until it reaches a labelled entity, a KOL wallet, a wallet with no funder, a loop, or the depth limit. Answers with server-sent events. Works on Solana and Robinhood Chain; the chain is taken from the address.

curl -N "https://api.scanner.net/funding-chain/stream?address=WALLET_ADDRESS&maxDepth=20" \
  -H "x-api-key: $SCANNER_API_KEY"

Events:

• start: { address, maxDepth, cached }.
• layer: { node }, once per hop. Depth 0 is the wallet you asked about. Each node has address, depth, fundedAmount, fundedAsset, fundedDate, signature, isBundled, bundleGroupIds and entity when labelled. On Robinhood Chain all layers arrive together when the trace finishes.
• terminal: { reason, terminalDepth, node }. reason is labeled, kol, depth, loop or no_funder. Robinhood Chain traces end with labeled, no_funder or depth.
• complete: { chain: { holderAddress, chain: [...] }, tracedAt }, with tracedAt in unix milliseconds.
• error: { error, code }, with code TIMEOUT or INTERNAL_ERROR.

Cost: 1 scan for a live trace, charged before it starts. A trace of the same address with the same maxDepth from the last 24 hours is replayed free, with cached: true. A different maxDepth is a separate trace. A failed trace is refunded, unless the connection was closed after layers had arrived.

The two 400 bodies are { "success": false, "error", "code" }, without requestId.

Cross-chain lookup

GET /cross-chain/{address}

Bridge transfers to and from a wallet, gathered from bridge providers. Works for Solana and 0x addresses.

curl "https://api.scanner.net/cross-chain/WALLET_ADDRESS" \
  -H "x-api-key: $SCANNER_API_KEY"

Response: { "success": true, "address", "transfers", "complete", "providers", "checkedAt", "missing", "cached" }.

• transfers: newest first, at most 500. Each has id, source (the bridge), status (pending, success, failed, refunded or unknown), createdAtMs, sender, receivers, src and dst legs (chain, chainName, tokenSymbol, amount, txHash), amountUsd and direction (in, out or self).
• complete: false when some providers didn't answer. providers gives answered and total, and missing how many failed. Use Retry to ask the missing ones again.
• cached: true when the answer came from a recent lookup.

A provider failure gives an incomplete result, not an error.

Cost: 1 scan for a live search, charged up front. It is refunded when no provider answered. stored=1 and cached answers are free.

Cross-chain retry

POST /cross-chain/{address}/retry

Asks again only the providers that failed in the wallet's latest live lookup, and returns the merged result. Free. No body.

curl -X POST "https://api.scanner.net/cross-chain/WALLET_ADDRESS/retry" \
  -H "x-api-key: $SCANNER_API_KEY"

Response: the same shape as the lookup, with cached: false.

Each wallet can be retried once every 30 seconds. The limit is per wallet, shared by every caller.