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%daydreams342d ago0xcf6cac…2a1448
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0xb8c441…867bc9
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x574c03…52e074
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x2785cc…70f7fa
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x897dbe…f261ee
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x2f15ce…608620
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x7efce4…227c51
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x386aba…cd505a
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x08b194…a4d4c9
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x581ec8…88731f
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams342d ago0x136417…031319
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0xd35674…5839ad
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0xbf8b3c…ea0837
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0xe2028a…4f1878
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0x204a65…93e9ad
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0xf3449a…434478
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0x0c988f…8f8aff
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0xe4a8e5…1c2e3c
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0x27e9e4…49403e
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0x3b011e…63e8bb
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams343d ago0x242a16…61c0c4
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0xa40dbc…e53fcf
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0xe076f7…49b71d
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x9d6509…bd6945
0xa9e2…19540x6482…b779BaseBase$0.0001100%daydreams344d ago0x7db355…1e964e

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.