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 $3067.84M Roundhouse has indexed across 1,401,919 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%daydreams337d ago0x816aea…e50223
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0xf93fa3…b41b9a
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0xf13542…b8f4c0
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0xaa2829…4579f7
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0x069d16…e7ba65
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0x722344…a53c9e
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0x242854…38914a
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0x5b7f02…4a2a68
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams338d ago0xa6f283…304203
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams339d ago0x213036…540fb4
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams339d ago0xc31bcd…89b36b
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0xfdf0f6…edb291
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0x48ccc5…900de6
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0xf21df0…0de773
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0x1fdda7…3af8b9
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0xbcc3d8…c63114
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0x736567…c6d992
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0x853007…f9beb3
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0x39b3a1…1a3a41
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0x7e1b93…6b7819
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams340d ago0xe15583…8dd500
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams341d ago0x6b5a52…907050
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams341d ago0x33c609…96de81
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams341d ago0x4c37bb…125d05
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams341d ago0x05ffbd…a4a8f4

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.