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,563 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 277d 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.00261277d 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%daydreams353d ago0x0d1261…bcbea7
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams353d ago0x20879f…1c8e54
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams353d ago0xd136b6…22a381
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams353d ago0x80998f…9b4c84
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams354d ago0x3c52f6…22edef
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams355d ago0x0508a1…d10396
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams355d ago0x990096…a7dac5
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams355d ago0x426fd7…a2c8b0
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams355d ago0xd5546a…ecb205
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams356d ago0xa2413f…12b62f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams356d ago0xd5818a…28f635
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams356d ago0xb3873e…5c0010
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams356d ago0xb1b2c3…d14515
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams357d ago0xbe0fc4…d86e16
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams357d ago0x50f538…dac5f2
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams358d ago0xa4419a…01764d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams358d ago0xfb815b…f5f5e4
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams358d ago0xcf007c…578e9e
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams358d ago0x7d7415…1ebe7d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams358d ago0xdbf6e9…805bbc
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams359d ago0x80fba0…cac20d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams359d ago0x152da6…621381
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams359d ago0xcdea53…610f8d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams359d ago0x8a31c7…6f3f01
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams360d ago0x147255…64f3f7

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.