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 $3059.84M Roundhouse has indexed across 1,397,496 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.000689100%questflow357d ago0x72d237…b89847
0x8095…423c0x4540…2b43BaseBase$0.000706100%questflow357d ago0x8bda51…50f657
0x8095…423c0x4540…2b43BaseBase$0.000562100%questflow357d ago0xdd3b63…3e33c3
0x8095…423c0x4540…2b43BaseBase$0.000691100%questflow357d ago0x1e69e5…c7151b
0x8095…423c0x4540…2b43BaseBase$0.000676100%questflow357d ago0x76b341…998a56
0x8095…423c0x4540…2b43BaseBase$0.000691100%questflow357d ago0x151816…59f4a7
0x8095…423c0x4540…2b43BaseBase$0.000676100%questflow357d ago0x785dbe…3afbc3
0x8095…423c0x4540…2b43BaseBase$0.000704100%questflow357d ago0xf6896f…a20caf
0x8095…423c0x4540…2b43BaseBase$0.000695100%questflow357d ago0x65621f…9166ab
0x8095…423c0x4540…2b43BaseBase$0.000686100%questflow357d ago0xb78383…6598b8
0x8095…423c0x4540…2b43BaseBase$0.000693100%questflow357d ago0x9a24d6…54076e
0x8095…423c0x4540…2b43BaseBase$0.000684100%questflow357d ago0x8f2b0f…9646b3
0x8095…423c0x4540…2b43BaseBase$0.000691100%questflow357d ago0x007709…4d14bb
0x8095…423c0x4540…2b43BaseBase$0.000687100%questflow357d ago0x3052ce…13097a
0x8095…423c0x4540…2b43BaseBase$0.000693100%questflow357d ago0x46a3f6…460f21
0x8095…423c0x4540…2b43BaseBase$0.000687100%questflow358d ago0x7aef6e…08e61e
0x8095…423c0x4540…2b43BaseBase$0.000693100%questflow358d ago0x9de03b…554a1b
0x8095…423c0x4540…2b43BaseBase$0.000689100%questflow358d ago0x74847a…6ab217
0x8095…423c0x4540…2b43BaseBase$0.000693100%questflow358d ago0x23eba9…d8bcbf
0x8095…423c0x4540…2b43BaseBase$0.0007100%questflow358d ago0x8e66a7…5924a1
0x8095…423c0x4540…2b43BaseBase$0.000174100%questflow358d ago0xb5e22b…82c570
0x8095…423c0x4540…2b43BaseBase$0.000688100%questflow358d ago0x88b347…accff9
0x8095…423c0x4540…2b43BaseBase$0.000696100%questflow358d ago0x82fe62…d58190
0x8095…423c0x4540…2b43BaseBase$0.000689100%questflow358d ago0xc18eae…4de449
0x8095…423c0x4540…2b43BaseBase$0.000707100%questflow358d ago0x089320…a51d17

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.