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%daydreams344d ago0xcd1026…41b858
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0x8b488c…0717a7
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0xa33182…729efd
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0x0b850b…0a11e2
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0x0acc55…78ab8c
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0x808f52…81e730
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0x9a7608…4bc8ee
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0xa345eb…ff0959
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams344d ago0x800470…62899f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0xd0c728…e3fb41
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0xa32792…850e4d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x66012e…1bf6ff
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0xfcc1ec…cee6ac
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x388efc…9c5645
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0xfa1b63…c9a1f8
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0xdb965a…9b4022
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x0b3580…32b283
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x9f5986…b3aaf5
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x2305d7…c0088f
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x35723c…e9e34d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams345d ago0x1a6fd4…de35e1
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams346d ago0x180a2d…a96d14
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams346d ago0xbcc8a8…03466d
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams346d ago0xe0932a…865d8b
0xa3b6…e2a40x6482…b779BaseBase$0.0001100%daydreams346d ago0xd8559f…a444d5

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.