AgentReport

0x2a1e…209c

0x2a1e44f0e127721d098c0a2dbde807cdbc3e209cExplorer
Paid out
$0.26
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
28
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $0.26 of the $847.23M Roundhouse has indexed across 1,330,946 wallets — less than 0.0001% of it.

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

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
Web & Content89%$0.2341
Not in any catalogue11%$0.03242

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 3 of 3 the amount paid narrows the list to the ones listed at that price.

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

MayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x4df6…cdea$0.23$0.00414d agoGraph
0x52e2…f3ea$0.02$0.002114d agoGraph
0x9baa…d6ed$0.006$0.00320d agoGraph

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

Data quality

89% of observed volume is with a single counterparty, in all 28 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2a1e…209c0x52e2…f3eaBase$0.001100%coinbase22d ago0xd44201…7d0501
0x2a1e…209c0x52e2…f3eaBase$0.001100%coinbase22d ago0xd1cadb…5dc68c
0x2a1e…209c0x52e2…f3eaBase$0.001100%coinbase22d ago0xe0e862…49ef9c

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

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

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: 0x2a1e…209c

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