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 $3068.58M Roundhouse has indexed across 1,402,563 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 277d 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.00259277d 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%daydreams344d ago0x16a964…366038
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x1f34ce…df3a83
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0xc3a415…b85008
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x8d8c10…7f0537
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x61b5b5…74cde4
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x72b938…f990bd
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x3088fa…dae4f6
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x366578…eb7f46
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0x28b049…ddd201
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0x3c5db8…d73180
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0x0ac79b…3e534d
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0x0ff657…a725c4
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0xbaa876…e8c5c9
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0xc33ab4…e2fc66
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0xb69ceb…51cf34
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0xd1a4ae…e776ce
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0x25010e…b87d2f
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0x62193a…68f56e
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams345d ago0xf3b5ed…c2f59a
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams346d ago0xf96b00…64e9ae
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams346d ago0x7beb4d…9fa669
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams346d ago0x445c95…6d5db1
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams346d ago0x33995d…6266e2
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams346d ago0xf06468…33d95e
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams346d ago0xe66c9f…5705ce

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.