AgentReport

0x0497…0f9d

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

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

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

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

$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
    263 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.00263276d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x219419…5322b6
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x294a6d…7e5482
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xca3ec2…c351bc
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb159cd…cfd290
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x1ae5fc…188d44
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x4ccee2…1b35a5
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x051e97…3baa56
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x357548…da54eb
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xfba8ea…8f4f14
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x01a01f…06d371
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x8f5158…822cf6
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7c5222…a1dabd
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams353d ago0xccd299…bc049a
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x3843b3…732f2a
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa13110…f05329
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams353d ago0xc55a01…ac60c3
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams354d ago0xf06258…86f69b
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams355d ago0xdeb681…8d49b8
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams355d ago0xaaf745…8d22c6
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x0cfa35…31653d
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x016aff…5a35b0
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x8c65a4…5c8223
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams355d ago0xafc276…2d225e
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams356d ago0x60a439…1ac01b
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams356d ago0x72e805…73e7af

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

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

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: 0x0497…0f9d

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