AgentReport

0x4540…2b43

0x4540fbcdc4f683f690383756ae1aa451148e2b43Explorer
Paid out
$0.77
Last 7d vs prior 7d
Received
$0.69
Last 7d vs prior 7d
Settlements
710
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.77 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — less than 0.0001% of it.

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

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

$0.77 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.

  • 0x3577…ca8d · last paid 36d ago
    $0.77
    1 call

    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
0x3577…ca8d$0.77$0.00136d agoGraph
0x8095…423c$0.00$0.69709343d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

53% of observed volume is with a single counterparty, in all 710 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8095…423c0x4540…2b43BaseBase$0.000685100%questflow362d ago0x3cb32b…3fcdcf
0x8095…423c0x4540…2b43BaseBase$0.000688100%questflow362d ago0x5983d3…0be1a8
0x8095…423c0x4540…2b43BaseBase$0.000688100%questflow362d ago0x60ab4c…419f7f
0x8095…423c0x4540…2b43BaseBase$0.000683100%questflow362d ago0x051a14…4902ab
0x8095…423c0x4540…2b43BaseBase$0.000682100%questflow362d ago0x81508b…f745ad
0x8095…423c0x4540…2b43BaseBase$0.00068100%questflow362d ago0x5cd66f…3e9f19
0x8095…423c0x4540…2b43BaseBase$0.000689100%questflow362d ago0xcc5f92…d8aa79
0x8095…423c0x4540…2b43BaseBase$0.000694100%questflow363d ago0xccadb7…9b7a6f
0x8095…423c0x4540…2b43BaseBase$0.000685100%questflow363d ago0x27ff8f…46b8b3
0x8095…423c0x4540…2b43BaseBase$0.000676100%questflow363d ago0xa8a3d6…55b1c3
0x8095…423c0x4540…2b43BaseBase$0.000681100%questflow363d ago0x58bfe6…4b732e
0x8095…423c0x4540…2b43BaseBase$0.000692100%questflow363d ago0xd89f48…3a2d0a
0x8095…423c0x4540…2b43BaseBase$0.000693100%questflow363d ago0xbfd93c…49efd0
0x8095…423c0x4540…2b43BaseBase$0.000701100%questflow363d ago0xbebccf…9ba680
0x8095…423c0x4540…2b43BaseBase$0.000685100%questflow363d ago0xa62784…656f63
0x8095…423c0x4540…2b43BaseBase$0.00068100%questflow363d ago0xa2eec3…a16112
0x8095…423c0x4540…2b43BaseBase$0.000683100%questflow363d ago0xa62fa9…fb2e9c
0x8095…423c0x4540…2b43BaseBase$0.000709100%questflow363d ago0xc7b94c…8b65f7
0x8095…423c0x4540…2b43BaseBase$0.000683100%questflow363d ago0xe0bfd5…14df45
0x8095…423c0x4540…2b43BaseBase$0.000709100%questflow363d ago0xd92b90…4f8f5b
0x8095…423c0x4540…2b43BaseBase$0.000686100%questflow363d ago0x5de391…1ca02b
0x8095…423c0x4540…2b43BaseBase$0.000678100%questflow363d ago0x89e28c…062d26
0x8095…423c0x4540…2b43BaseBase$0.000691100%questflow363d ago0x32cf49…35fb54
0x8095…423c0x4540…2b43BaseBase$0.000304100%questflow363d ago0x4afe51…70642a
0x8095…423c0x4540…2b43BaseBase$0.000292100%questflow363d ago0x11e088…3fc364

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

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

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: 0x4540…2b43

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