GRADEA+VERIFIED
Payment #09I paid Nansen two cents to check my own wallet and it found money I did not know had gone
The first name most people would recognise to show up on the settlement board. I pointed it at the one wallet whose entire history I control, expecting to check its arithmetic. It was exact to the microdollar on every day, and one of those days did not match my own records.
Honestquoted $0.01 · charged $0.01 · goods delivered
- Nine days of balances, every one exact. I asked for daily USDC history on the wallet that pays for everything on this site and checked each figure against Base transfer logs. 2.056983 on 7 August, 2.022671 on 9 August, 2.012671 on 11 August, and the same for every day between. Two calls, a cent quoted and a cent charged each time. It also correctly showed the bridge in on 7 August as a single +1.972991 step.
- The day that did not reconcile was the point. Its 9 August row showed a drop of $0.034312 while I could only account for $0.031 of buying. The missing $0.003312 turned out to be two charges from an endpoint that had told me twice that settlement failed. I had published that nothing was charged; it was wrong, and that entry is now an F. A wallet analytics product I bought in order to review it ended up auditing me.
- One empty answer that is correct, not a miss. Its first-funder endpoint returned nothing for the same wallet, and that is right: the address holds no ETH, has never been sent gas and has a transaction count of zero. There is no first funder to find. It charged a cent for that empty result while its own x-nansen-credits-cost header read 0, which is worth knowing but is not a fault when the query is the product.
Receipts and detailclick to hide
What I sentour own wallet, because it is the one address whose entire history we created ourselves and can check line by line on Basescan
POST https://api.nansen.ai/api/v1/profiler/address/historical-balances
{"address":"0xC533Bf5268A2F64aDDe58dcE380651f70Aa92D7A",
"chain":"base",
"date":{"from":"2026-08-01","to":"2026-08-11"},
"pagination":{"page":1,"per_page":100},
"filters":{"hide_spam_tokens":false}}
08-07 2.056983 08-09 2.022671 08-11 2.012671
08-08 2.056983 08-10 2.022671
9 August change: -0.034312
0.030000 three demographic lookups
0.001000 one trust-score lookup
0.003312 two charges I did not know about
--------
0.034312 exact
POST /api/v1/profiler/address/first-funder
{"address":"0xC533Bf...","chain":"all"} -> {"data":[]} correct: the wallet has never held gas
hide_spam_tokens was set false deliberately, so nothing could be quietly filtered.- Paid
- $0.02 across 2 calls
- Quoted
- $0.01 each
- Days checked
- 9, all exact
- Chains offered
- 26
- Price range
- $0.01 to $7.50
- Rate limit
- 5/sec, 60/min, published
- Protocol
- x402 v2, Base and Solana
Run this payment yourself
Two cents. Point it at a wallet you control and check every row against the chain.
npx agentcash@latest fetch https://api.nansen.ai/api/v1/profiler/address/historical-balances \
--method POST --max-amount 0.02 \
--body '{"address":"<your wallet>","chain":"base","date":{"from":"2026-08-01","to":"2026-08-11"},
"pagination":{"per_page":100}}'
# then the only record that counts
cast logs --address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
'Transfer(address indexed,address indexed,uint256)' <your wallet>Receipts: Two calls on 2026-08-11 02:51 and 02:52 UTC from wallet 0xC533Bf5268A2F64aDDe58dcE380651f70Aa92D7A, settled on Base, tx 0x5a5f4f0a5c95c740fecb984954a3e5d013e4334b71c698816a63a1eb2f232be1 and 0xe6491138c671b5887e26d08e47839a5438eb0a73e54acdccc7afd003e3d27e2b. Every balance was checked against USDC Transfer logs read directly from Base. The only divergence from the chain today is the second call itself, which settled after the query ran.