AgentReport

0x2826…ee13

0x2826dfc929699f8c9f0e77a4e6cf199c835dee13Explorer
Paid out
$66.67↑ 89896%
Last 7d vs prior 7d
Received
$61.67↑ 76889%
Last 7d vs prior 7d
Settlements
1517↑ 9281%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $66.67 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.

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

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
Crypto Markets95%$61.069991
Not in any catalogue5%$3.1111

$3.11 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,103 most recent settlements of 1,517 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not. One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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
0x5fb2…efe5$61.06$61.671,1022d agoGraph
0x4eb6…9884$3.11$0.0014d agoGraph

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

Data quality

98% of observed volume is with a single counterparty, in the 1103 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Organic volume $125.85 of $125.85 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0xf05911…ed5cc3
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x5dd8ab…21bdda
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x77e78a…dfc659
0x2826…ee130x5fb2…efe5BaseBase$0.25100%payAI2d ago0x2fc194…f22284
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0xd00c50…ac14b4
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x288cf1…9d1758
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x013528…5d08cd
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x98169b…2f9a92
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x264455…b9fa0f
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0xc91cba…ac562b
0x5fb2…efe50x2826…ee13BaseBase$0.21100%payAI2d ago0x664d7b…0b59da
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0xc8302f…bfc9f6
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x4bfa2a…fbe120
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0xc58912…b8c626
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x89d8af…476409
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x3b78ec…7b29ac
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0x31bae7…8fe9dc
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0xf8f387…877cc5
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x01f0a2…c38dd4
0x2826…ee130x5fb2…efe5BaseBase$0.25100%payAI2d ago0xb8d577…f597e0
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0x892ca4…0c64aa
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x30bf64…2e4b6e
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0xd05fbe…d03185
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0xeffcc0…b8f97e
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x0f1d6a…e81645

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

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

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: 0x2826…ee13

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