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,401,091 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
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x45826e…74376e
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x5617ee…279f41
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0xb39810…7d538c
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x4cfdf1…389c69
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x093cfb…0f13c8
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0x6e0e6f…16e0ae
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0xfcfeab…fe71ca
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x6196b0…621316
0x2826…ee130x5fb2…efe5BaseBase$0.25100%payAI2d ago0x8df43b…471c67
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0x851f28…0c0d30
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0xfef10c…457394
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x4635cf…000807
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x7beb2c…2c8050
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0xcfbbc1…1db9d1
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x40c244…eb490e
0x5fb2…efe50x2826…ee13BaseBase$0.21100%payAI2d ago0xb90229…51f59c
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x6f5719…4ca376
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x61f777…2a8619
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x7d17f8…841cb6
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x6f8218…71ae4f
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0xa5f340…852684
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0x9001ca…fafd5c
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x07b156…2ca301
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0xf4d85b…2d8329
0x2826…ee130x5fb2…efe5BaseBase$0.25100%payAI2d ago0xd9170a…f7077c

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.