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,396 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%daydreams338d ago0xa7a0a2…6eb07f
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0x8b1949…083a39
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0x05a46f…935a71
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0x8f4168…949505
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams338d ago0x2e2544…759710
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams339d ago0x5f9a99…13222f
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0xf64650…5c839a
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0x370f8e…db53e5
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0xf45b58…c7b10c
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0xe84a25…622852
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0xcacaa7…0e02c2
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0x62336b…666c16
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0x06512a…984acc
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0xf122a2…689981
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0x06d33e…3d911b
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0xe74b8d…cba772
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams340d ago0x121993…130575
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0x8c5818…37d7c9
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0x9f2720…441cd9
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0xe68b1e…089d93
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0x78a6da…69d7ce
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0x28f1c7…440dea
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0x8d2c2a…6d8219
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0xc8c29e…38d594
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams341d ago0xd5e422…6b7ef9

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.