AgentReport

0x5f18…fa07

0x5f1811ed9ab75f531f9ad72a6bdc0c944c4bfa07Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
277
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 (277)

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

$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
    277 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.00277276d 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 277 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0xfa0b8e…6a064b
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0xa139cb…f5a6fc
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0x76c828…2ed879
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0x645176…4899f7
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0xec9df9…d3e22c
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0xcd4bb7…e12375
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0x1caf15…12c519
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0xc8ba6c…0ab893
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0xa4a084…6f2afd
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0x5a970c…6b3118
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0xc269dc…5e6415
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0x563452…df9a47
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0xe7e452…e502b9
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0xfbdf03…871687
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0x482032…e31180
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams352d ago0x303b7c…4723ba
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams353d ago0x369775…7e58fa
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams353d ago0x8b43b4…5841a5
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams354d ago0x3fe040…b1457e
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams354d ago0x1f7b65…2c1d64
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams355d ago0x13e0b5…80a89c
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams355d ago0x2f5526…465eac
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams355d ago0x74c4f1…02ae5f
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams356d ago0x9b811e…0130fd
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams356d ago0xea5c92…5215b3

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

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

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: 0x5f18…fa07

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