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.002100%payAI2d ago0x3b55d6…68c536
0x2826…ee130x5fb2…efe5BaseBase$0.25100%payAI2d ago0x75537b…85cac0
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0x9ee9d2…bf405f
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x805fe8…307f02
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x079bbb…acc6d7
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x9b6439…9722bf
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x23904d…f93a65
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x2614d7…be81f0
0x5fb2…efe50x2826…ee13BaseBase$0.21100%payAI2d ago0xef61ff…fff621
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0xd97902…79812e
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x99d098…d26f6f
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x94f325…25848c
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x04795e…87a074
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0x1ca079…664a14
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0xcfab33…0db1a8
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x2ad3b6…d90965
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0x58dc53…714a6a
0x2826…ee130x5fb2…efe5BaseBase$0.25100%payAI2d ago0xa3d7c9…39267a
0x5fb2…efe50x2826…ee13BaseBase$0.26100%payAI2d ago0xb23e82…d94d44
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x95005d…4d8a09
0x2826…ee130x5fb2…efe5BaseBase$0.05100%payAI2d ago0xd0b0d1…220b64
0x2826…ee130x5fb2…efe5BaseBase$0.01100%payAI2d ago0x39597a…99c0fc
0x2826…ee130x5fb2…efe5BaseBase$0.002100%payAI2d ago0xf81110…4a87c6
0x2826…ee130x5fb2…efe5BaseBase$0.10100%payAI2d ago0x490f27…0b6087
0x5fb2…efe50x2826…ee13BaseBase$0.21100%payAI2d ago0x03b444…8e6307

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.