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%daydreams343d ago0x34ed90…db9b0b
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0x545b8c…c6cbcc
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0x5f3ef8…43b45b
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb99813…75e927
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0x0c6552…41d8a6
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0x517047…0e87bf
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0x583de7…4c6344
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0xfdbaa9…699513
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0x103783…3dae93
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0xc30cf2…e20372
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams343d ago0xe3c6aa…27c00e
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x30c57e…ebffb1
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc88a27…5e3224
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x319dc0…8a0248
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x51cd1a…09dc14
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x997f29…79849a
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0xfe6d2d…201100
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x4cb614…e789da
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x04f69c…47daa0
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x829649…e34230
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0x28ad96…de0e16
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc5b34d…bcab96
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa1a391…9a7178
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams345d ago0xd4f6de…9225e6
0x0497…0f9d0x6482…b779BaseBase$0.0001100%daydreams345d ago0x23ec1f…3f6d18

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.