AgentReport

0xf383…80a9

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,575 wallets — less than 0.0001% of it.

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

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

$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
    278 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.00278276d 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 278 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams351d ago0xe261ae…2e56a3
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0xf63e75…44a5bc
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0x8ce218…3cd87e
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0xb49292…c5c934
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0xe5797d…3f8c34
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0x7f2ac2…63030e
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0xb15920…6d3f73
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0xaa38e8…ed02ec
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0x89aafd…232b47
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams352d ago0x591007…7a9999
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams353d ago0x86520c…38bad1
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams353d ago0x4ae9a5…fb5f87
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams353d ago0xd9c892…ff44d5
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams353d ago0x87cb39…981bb1
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams353d ago0x5cfa71…286b2c
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams354d ago0x50bbe0…a1153b
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams355d ago0xffb640…9af41b
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams355d ago0x510078…e8a8bd
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams355d ago0x14eb8d…0d74a6
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams355d ago0x554905…2149e3
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams355d ago0xc03dc0…35b204
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams355d ago0x5d5358…d216ad
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams356d ago0xe7dc08…7db1a3
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams356d ago0x066482…c08b34
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams356d ago0x0a99e3…5ad6e2

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

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

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: 0xf383…80a9

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