AgentReport

0xbaa6…5397

0xbaa6a2309c4d2c7b15c9e4a67e1fccbecad45397Explorer
Paid out
$0.002895
Last 7d vs prior 7d
Received
$0.002098
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.002895 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.

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

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

$0.002895 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.

  • 0x3577…ca8d · last paid 37d ago
    $0.002895
    1 call

    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
0x3577…ca8d$0.002895$0.00137d agoGraph
0xd87d…44a4$0.00$0.0020984341d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

58% of observed volume is with a single counterparty, in all 5 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbaa6…53970x3577…ca8dBaseBase$0.00289570%0x642b…6c7537d ago0xd578ef…72cbe5
0xd87d…44a40xbaa6…5397BaseBase$0.001402100%questflow341d ago0x1afa68…258141
0xd87d…44a40xbaa6…5397BaseBase$0.000217100%questflow345d ago0x6bc95e…cdccef
0xd87d…44a40xbaa6…5397BaseBase$0.000246100%questflow353d ago0x3b0a78…fc60c8
0xd87d…44a40xbaa6…5397BaseBase$0.000233100%questflow354d ago0xa534d2…ddec64

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

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

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: 0xbaa6…5397

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