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,510 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%daydreams343d ago0x14e435…98836a
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0xf2282b…12c7ac
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0x1fd689…72dbaa
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0x0e2cd9…d9ebd0
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0x1d95bd…781593
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0xfddb1f…5ee1fa
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0x9be5dc…9490c9
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0x6fbe5f…dd4bed
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0xec2c25…1c6532
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams343d ago0x3f1682…6b911a
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x4b7ff3…eaf74d
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x0512c4…ffad91
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0xeef534…26e98e
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x933857…c473fc
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x37debf…e5d3c5
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0xe65d8c…573a6c
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x3256f3…8f6c92
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0xc26861…40f638
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x6e64c0…616d29
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x7d6ca4…1fbbd0
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams344d ago0x671247…c2c9ae
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams345d ago0xc9162c…732f18
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams345d ago0x4bb3a5…34e929
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams345d ago0x9c67cd…134f17
0x5f18…fa070x6482…b779BaseBase$0.0001100%daydreams345d ago0x274b75…0db946

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.