AgentReport

0xf39f…61b9

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    280 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.00280277d 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 280 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0xd669dd…38075a
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0xd01dc4…2eb92f
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0xf9c2c6…fb9133
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0xd61311…62f2c7
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0xde9f8a…0c6e01
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0xb8ac43…ce526e
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0xa3ccc9…98d702
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0x808b0a…86e36f
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0x2c8546…1678e0
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0x09ac70…91cd35
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0xaddfdb…35007d
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0xc93e6d…c2b95f
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams353d ago0xd4ff82…76626a
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams354d ago0xda4506…f19806
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams354d ago0x55d9c6…b32557
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams355d ago0xfadc5d…fc4096
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams355d ago0x3332d0…a010db
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams356d ago0x1e1bb9…aa6165
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams356d ago0x146764…caa226
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams356d ago0x311c28…4430d4
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams356d ago0xb627dc…fcb50d
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams357d ago0x3c237b…10dc44
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams357d ago0x550db9…72f2e7
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams357d ago0xe11f73…fcd468
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams357d ago0x22fc41…63a490

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

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

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: 0xf39f…61b9

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