AgentReport

0xa9e2…1954

0xa9e29ed35f0c653634a1f9fea77bdff28e8d1954Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
259
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,402,228 wallets — less than 0.0001% of it.

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

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.032591

$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
    259 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.00259276d 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 259 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0x6d8386…b8c663
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0xd3a1e5…f97102
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0xf8d6e2…b93b17
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0x45e71f…630d58
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0x9211dc…0e4429
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0xedb3a3…4e888e
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0x2c9ddb…6c40bc
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams326d ago0xc9c5f7…d3efe7
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams327d ago0xfe3e84…8701f7
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams327d ago0x4116ef…ca7b71
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams327d ago0x434d8b…6575d5
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams327d ago0xa915f6…55c8a6
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams327d ago0x23bce5…a0559c
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams327d ago0xcb0b8d…ba581f
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams328d ago0x2a4582…fc680f
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams328d ago0xd7c778…fbfcf5
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams328d ago0xa6068f…82c884
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams336d ago0xd893c3…181e55
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams337d ago0xf16fdd…6dbd70
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams337d ago0x1420b0…0311ef
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams337d ago0x2ff222…d1d0c3
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams337d ago0xa2c788…809060
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0x1925b9…18955b
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0xe6f767…b15620
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0x327ec6…0f5487

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

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

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: 0xa9e2…1954

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