AgentReport

0xadd4…2f01

0xadd4b0872d53e0920939956eb008e19d68e52f01Explorer
Paid out
$1.21↓ 6.4%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
1214↓ 6.4%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.21 of the $3059.84M Roundhouse has indexed across 1,397,384 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%$1.001,0002

$1.00 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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xfe80…47ee · last paid 8m ago
    $0.66
    656 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 96d ago
    $0.34
    344 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfe80…47ee$0.66$0.006568m agoGraph
0x9c95…e299$0.34$0.0034496d agoGraph

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

Data quality

66% 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
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa18h ago0x7d2a2a…d8bd0f
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa19h ago0xe36258…ab1202
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa19h ago0x7638ba…a4ee09
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa20h ago0x18a5be…d4d42f
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa21h ago0x2c4a95…96ac27
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa22h ago0x0825b7…e2dd27
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa22h ago0xf9d94b…7dc2ec
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa23h ago0x8a1a77…c35bfc
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x5fb2c1…ae9a3d
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x1aa470…ef7bdb
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x479971…2f4a48
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x619460…904768
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x836ee4…01156d
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x862217…d81275
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x117b1a…24be01
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0xc55eab…6583df
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x1345b9…4a21ab
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x4be912…b8e6cd
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0xb0b3af…427331
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0xc6ad56…a0c5b3
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0xd604aa…212986
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0xa0a3d4…13b4c2
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x286be6…e52296
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0xf6095f…bf21fe
0xadd4…2f010xfe80…47eeBaseBase$0.001100%fluxa1d ago0x2d3e69…425ad8

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

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

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: 0xadd4…2f01

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