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%daydreams328d ago0xc0fcae…93a055
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams335d ago0x08138b…d2f87c
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x708ba8…7cc0ab
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams337d ago0xc2b8ce…ae54d3
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x4508f6…255b8e
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x5de9ad…2df057
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x1e7a21…a631ef
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams337d ago0xfb9b7c…098a4f
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams338d ago0x061660…c79e98
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams338d ago0x20e6c3…8c00ba
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams338d ago0x2ec43b…1e17e4
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x9bd0fa…752332
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x6da9f9…56b3a9
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams339d ago0xbeecbe…d56192
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x0be899…e9cf5c
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x25832d…072a5b
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x8d2c4c…3e2e06
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x87fce5…d231b6
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1e9c48…815a5b
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2b9eb6…c073ed
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x74056a…275e77
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x968fcf…f81854
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x26117c…8dcd92
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa6a292…8411fc
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams340d ago0xfcd33a…09b947

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.