AgentReport

0xae49…20b3

0xae4912b7b6950b5df476a6f4a23e9b195b0920b3Explorer
Paid out
$34.10
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21826
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.10 of the $260.71M Roundhouse has indexed across 716,404 wallets — less than 0.0001% of it.

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

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%$3.511,0002

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

Folded from this wallet's 1,000 most recent settlements of 21,826 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.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.01$0.00850225d agoGraph
0x8324…fd0e$1.50$0.00150238d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0xf6a89a…7a043a
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x0aa3fa…1444cd
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x7c3cd5…f3301f
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x6496cf…9f9640
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0xe17d8a…8fd0ed
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x8187af…5fec97
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x84ac44…4f892c
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x4cbde5…f5248f
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x2da9c2…be2c67
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x92d65c…4f38cb
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x9df5d1…987192
0xae49…20b30x0495…eed9Base$0.01100%payAI225d ago0xb078eb…0c18c7
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x20339b…323201
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x697437…a2ba26
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x6aa248…3ffb79
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0xc8855e…4bade4
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x3bd701…a7aaa1
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x8e1c0b…7948b7
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0x78d66d…8fe4e5
0xae49…20b30x0495…eed9Base$0.10100%payAI225d ago0xb034f7…97befb
0xae49…20b30x0495…eed9Base$0.01100%payAI225d ago0x7d67a9…62b479
0xae49…20b30x0495…eed9Base$0.01100%payAI225d ago0x78762a…0c1635
0xae49…20b30x8324…fd0eBase$0.01100%payAI238d ago0x1d37a7…3cc2eb
0xae49…20b30x0495…eed9Base$0.0001100%payAI238d ago0xe7b70d…14fd5f
0xae49…20b30x0495…eed9Base$0.0001100%payAI238d ago0xc672f7…c3bebc

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

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

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: 0xae49…20b3

curl -s 'https://api.roundhouseai.io/v0/agents/0xae4912b7b6950b5df476a6f4a23e9b195b0920b3'
curl -s 'https://api.roundhouseai.io/v0/entities/0xae4912b7b6950b5df476a6f4a23e9b195b0920b3/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.