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%daydreams341d ago0x5dff15…e3142f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0xbf51f4…9896fd
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams341d ago0x2c1553…4193f9
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0xaf4993…4a1e99
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0xb559dc…db50c9
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0x5911ae…0adcd5
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0x162927…3f12cc
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0x1d3105…99dbbb
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0xbbee6a…7c35da
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0xe3edc6…d1139d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0xb24585…3e43eb
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0x1d1959…c5254d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0x74ac27…387dd3
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams342d ago0xdbc126…809c81
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x945bfb…784f7f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x9f2984…842d14
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x7591f0…5ca32e
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0xdd747f…a875fa
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0xe4ae2a…446888
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x29862d…fedd1f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x182134…85c313
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x670455…e71aba
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x9632f2…d3eefa
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x415b74…3efb01
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams343d ago0x4c83ee…c01473

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.