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,563 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%daydreams348d ago0x72d7a8…53adda
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams349d ago0x65b6d4…f87d66
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams349d ago0xe39c3b…c83641
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams349d ago0xfae5ff…989d98
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams349d ago0xd8f1ae…4c0275
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams350d ago0x22aec3…e4b517
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams350d ago0xd91b63…5105ad
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams350d ago0x0e9afb…cd1dd6
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams350d ago0xa0c8fd…0ffb7a
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams350d ago0xee2729…7eeb98
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams351d ago0xf8ab16…35c9d0
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams351d ago0x2275f9…e8c48e
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams351d ago0x31f654…c3c349
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams351d ago0xfae70c…5523e5
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams351d ago0xb4a5b5…eff2a2
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams351d ago0x762fcd…80f1af
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0xd08607…8c1e9e
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0x7aaa78…2b832b
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0x898b6e…431a64
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0xfd33b6…144fc5
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0x4b58d2…24a992
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0xb81c49…120d14
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0x5555ee…96b699
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0x85657a…65018c
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams352d ago0x6dce6b…838ac7

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.