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%daydreams343d ago0x8d7109…7cd631
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams343d ago0xac7f54…162d9c
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x5f577f…7e5e55
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x19403a…2cdf5e
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0xac4bdd…ab8af6
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x938ec8…bb82b4
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x301878…1bdab7
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0xa60ee9…165361
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x8e9ecf…8b60be
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0xc18c2b…9adce6
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x292c3c…30c051
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0xefd9cb…cbac1e
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams344d ago0x9cba1a…1da44c
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x059bc8…694e6c
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0xde3083…f01e13
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x7238fd…f3870a
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0xd3f563…e585de
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x27905a…646c2f
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x1c10a1…ede24d
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x2120dc…abd42d
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x7372b8…41d0af
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0xf07792…43e2c8
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0xf1de19…a35814
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams345d ago0x97f86d…1cba58
0x2a73…ad460x6482…b779BaseBase$0.0001100%daydreams346d ago0x4f2f42…a3b369

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.