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.17M Roundhouse has indexed across 1,400,092 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%daydreams323d ago0x4c74f7…1dab93
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0x156a1a…bfc62b
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0x2698f2…071ebe
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0x2590a5…e7bf91
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0xe3e24e…e123f1
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0x1f297b…2b35a3
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0xb29de7…b7a06d
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0xd47076…772d8c
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0x6983de…266471
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams323d ago0xd62d44…fdc402
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0x81608a…bef4b2
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0xfdfec5…9fe8fd
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0xb91850…91b75d
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0xa7c9c0…ee56a1
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0xf35879…e1fc87
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0x64a500…190630
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0xa75233…1f86ad
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0xed27d2…aec011
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0x0f0f4b…7da07c
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0x946351…6a1427
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams324d ago0x359e34…d31670
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams325d ago0x9358e1…3aad06
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams325d ago0xa7a11f…89aa37
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams325d ago0xf5f61d…2af6d0
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams325d ago0x5310ba…9f2851

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.