AgentReport

0x0082…ba80

0x0082f65502aa92c5c3fdf6761919fde0b652ba80Explorer
Paid out
$1.51↑ 48%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
1506↑ 48%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.51 of the $3066.54M Roundhouse has indexed across 1,400,510 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 22m ago
    $0.73
    730 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 110d ago
    $0.27
    270 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,506 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.73$0.0073022m agoGraph
0x9c95…e299$0.27$0.00270110d agoGraph

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

Data quality

73% 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
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa22m ago0xc039a9…dd442d
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa1h ago0x273436…5f8318
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa2h ago0x90226f…12e8cb
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa3h ago0x725d13…5dbaa8
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa4h ago0xf56325…038c35
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa4h ago0xe43e72…743b32
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa5h ago0xbedb24…b9ce97
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa6h ago0xcb437a…3e0185
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa7h ago0xf78aa4…d20c9f
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa8h ago0xc98ae9…f68af4
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa9h ago0x3be3ff…725267
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa10h ago0xa3b0fb…af4868
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa11h ago0xf29c8b…3b3b13
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa12h ago0xab5bed…0ab273
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa13h ago0x3b222b…b8f601
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa14h ago0x8b0172…39e8cf
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa15h ago0x262af4…cc00eb
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa16h ago0x332ceb…70b501
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa17h ago0x1bd70b…1010cc
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa17h ago0xab6728…ee87ee
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa18h ago0x3913cb…9a7d2d
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa19h ago0x8d12a3…c467c7
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa20h ago0xd37281…c95065
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa21h ago0x000d5c…7c6f5c
0x0082…ba800xfe80…47eeBaseBase$0.001100%fluxa22h ago0xf437ea…d077b9

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

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

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: 0x0082…ba80

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