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,689 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%daydreams340d ago0xfbbae0…f4ad60
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3f702b…100c41
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0xad387e…58c5b2
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x08e2e9…74aff3
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x34c66f…480ae2
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2a3826…d9bd36
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x84bf78…e57dd9
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x8e6cca…90ef44
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0xd24142…d524ff
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x899ea8…ab7f92
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x52a38f…9f5fc3
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0xc946df…a34a85
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x0780f0…5e6218
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams341d ago0x6a21b9…189400
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x548a5a…e4b844
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x967216…2ed959
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0xd696f1…e71db3
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x80428f…5f61ec
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x2eaa1d…bad6b0
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x1405f0…797203
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x1d38fa…ed7ffb
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x432bfe…dcb894
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x09646e…495fcc
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0xf34ddf…58f451
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams342d ago0x899d26…71ad59

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.