AgentReport

0x0dfa…4cf7

0x0dfa1e898f21a9b50b61ef8928b434869b244cf7Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
262
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,255 wallets — less than 0.0001% of it.

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

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams343d ago0x23304f…fb8922
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams343d ago0x4fcb1a…fa894a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams343d ago0x0befba…c676a3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams343d ago0xce5884…ce55d9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams343d ago0x723993…fed60a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x5acbcf…31b894
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x4dc26e…b059d7
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x9b39dd…877c28
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x267d17…e0961d
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x7f1fd5…b7d1dd
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0xfb71cd…712c40
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x6373a3…5387d7
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0xec2709…1749de
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x432bc0…a5e6f3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x99fb76…11f79a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x438c24…b0cd04
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams344d ago0x0e7daf…3788c9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0xb459c1…ee366f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x547d78…f0b81a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0xa6efa6…fb1116
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0xa1932d…b67b2f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x0e4582…528bde
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0xb750dd…c7896f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x09b6d0…d9ee31
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x1423e6…cb797e

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

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

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: 0x0dfa…4cf7

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