AgentReport

0x231d…b36a

0x231d52de545807ded0619496cb141c0c112fb36aExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
260
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.25M Roundhouse has indexed across 1,401,192 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (260)

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

$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
    260 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.00260276d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x9af461…bf190b
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x254362…9bbb1d
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x906a25…12fc40
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbb4325…866339
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x65919a…83b287
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams353d ago0xc19e1f…afeae1
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x0ba703…545cfd
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams354d ago0x7a84aa…9d5563
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams354d ago0x368390…66cd26
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams354d ago0x9cc472…e79d30
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x7d7683…844010
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa59e8d…121539
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams355d ago0xf65890…616bea
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x875d3e…63dc45
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams356d ago0xb3c5b6…1e40a0
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams356d ago0xf463b7…46aaf9
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x573286…c4964c
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x2fa171…4dd57a
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x525581…95a769
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x3601dc…e1e189
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams357d ago0xad0216…7f8482
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x6d8e3f…5340b4
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams358d ago0x4a1c7c…8beba4
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams358d ago0xf0bfbb…6b463a
0x231d…b36a0x6482…b779BaseBase$0.0001100%daydreams358d ago0xcef67f…9a92b0

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

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

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: 0x231d…b36a

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