AgentReport

0xa3b6…e2a4

0xa3b663fd55cfb9ec6063fac8fc35de4e62a8e2a4Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
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 (261)

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

$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
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams338d ago0xdd1e9e…ea4dd8
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams338d ago0xec97da…011182
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams338d ago0xb00ef3…5d76ea
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams338d ago0x241263…05976b
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams339d ago0xdf0c5c…f4e238
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams339d ago0xa83dba…140d9b
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0x6aa127…4fdbc8
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0x9458da…3cfa2b
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xba636d…54249a
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xf53e73…9b6578
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xbfe2ca…afa05c
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xdf86c1…641ef5
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xd65b05…edab57
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xb6384b…7dd9e4
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xb1b37d…0f3eab
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0x868dd2…fc77b6
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0x7b7fbb…690ec0
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams340d ago0xe43545…a8d13c
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0x83025e…9bfa0f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0xe22191…67970d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0x71b090…0de4c7
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0xb191bd…9babb1
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0xf7c617…5144de
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0xbdfec9…2c1104
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0xbb3310…6998cb

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

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

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: 0xa3b6…e2a4

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