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%daydreams348d ago0x243754…dee916
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x56dd12…628a8a
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0xff8f9b…d606bc
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x7fd47e…26bceb
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x13ee54…16ed5f
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x7441b3…433b01
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x8a8d53…49e3ea
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x34cc83…f7fbe7
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x01432e…7797fc
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0x4360e3…c6ddfe
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams348d ago0xa3f73c…a7d5f0
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0x223e7e…c6352d
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0xe46542…e33fca
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0x68ded7…d078a1
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0x48473e…21a2a9
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0x7abbaf…c919b1
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0xed6a08…458e4a
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams349d ago0x839dfe…c00884
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams350d ago0x166977…bd7e31
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams350d ago0xda00a0…2333fd
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams350d ago0x7f3dab…d328ac
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0xe494e0…34de5a
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0xe380c5…043a75
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0xa45759…c63abb
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams351d ago0x9c674e…f431b9

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.