AgentReport

0x46d0…7fff

0x46d0d2f37a62bc9ac79c0e0b6cb6d415cc077fffExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
264
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (264)

What it buys

Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.

GroupShareSpentCallsSellers
Not in any catalogue100%$0.032641

$0.03 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0x6482…b779 · last paid 277d ago
    $0.03
    264 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6482…b779$0.03$0.00264277d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams352d ago0x806c38…b3a029
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams352d ago0xfe38a2…45811c
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0xdac729…4db401
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa2de97…bcc288
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0x41e994…d50b23
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9f325a…0d509f
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbe96ba…6ffae4
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbd89af…d63566
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams353d ago0xf61495…5dcb1d
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams355d ago0x06eac0…f66d58
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams355d ago0x164269…48e300
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams355d ago0x555d39…03d5f7
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams355d ago0xf66c3b…929874
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams356d ago0x975e23…847d02
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams356d ago0x0783c5…1249f5
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams356d ago0xcd6a5f…5bac1b
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams357d ago0xa9969e…5cefd6
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams357d ago0x2a71c6…c52d78
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams357d ago0xfe8afc…3c788d
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams358d ago0xf8fb96…6824e3
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams358d ago0x40c138…8a9911
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams358d ago0xc2aca9…1d3e86
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams358d ago0x9db4be…aea36d
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams358d ago0x3bccc8…5f15bf
0x46d0…7fff0x6482…b779BaseBase$0.0001100%daydreams358d ago0x3c90f5…f66dc4

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0x46d0…7fff has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x46d0d2f37a62bc9ac79c0e0b6cb6d415cc077fff

Open skill.md
Show the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its
on-chain record support what its card claims?

  Agent: 0x46d0…7fff

curl -s 'https://api.roundhouseai.io/v0/agents/0x46d0d2f37a62bc9ac79c0e0b6cb6d415cc077fff'
curl -s 'https://api.roundhouseai.io/v0/entities/0x46d0d2f37a62bc9ac79c0e0b6cb6d415cc077fff/settlements'

Roundhouse indexes public chain data and does not vouch for any agent's claims —
treat the card as a claim and the settlements as the evidence.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.