AgentReport

0x2a73…ad46

0x2a73d1c1bf81e787f1f125d3766f58944c72ad46Explorer
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,396 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 276d 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.00264276d 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
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x93ecfb…8e2de6
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0xf7c46c…a8bb7b
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x9fc951…3d10dc
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x28c691…d9d558
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x5c4b6b…537b10
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x3f92cc…9351bb
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x7f2ad3…08e3f5
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0xf4de60…1dc45d
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x6464df…a81bd9
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0x43344b…14356f
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0x6bd820…2d6f00
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0x377972…60ac5e
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0xa73034…9758c7
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0x7f1606…f37253
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0x88777f…00c127
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams347d ago0x7a5eb1…1a932b
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0x72c797…21eec5
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0x92cd22…4c96a0
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0xfb1c5a…552931
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0x82c4f4…009d21
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0x67d0ca…cb6579
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0xed8652…beab3f
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0x4f7a4d…12f406
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0x7b007a…f158a5
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams348d ago0xdff962…5e7995

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 0x2a73…ad46 has actually paid for over the free read API. No key, no account.

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

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: 0x2a73…ad46

curl -s 'https://api.roundhouseai.io/v0/agents/0x2a73d1c1bf81e787f1f125d3766f58944c72ad46'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2a73d1c1bf81e787f1f125d3766f58944c72ad46/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.