AgentReport

0xa361…cab1

0xa361396282700ea8bc629de0d74253f6b7c8cab1Explorer
Paid out
$1.41↑ 55%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
1414↑ 55%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.41 of the $3061.41M Roundhouse has indexed across 1,398,509 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 24m ago
    $0.67
    674 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 104d ago
    $0.33
    326 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,414 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.67$0.0067424m agoGraph
0x9c95…e299$0.33$0.00326104d agoGraph

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

Data quality

67% 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
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x8625af…549afc
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x4eb7f1…40d03f
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x979380…b21f95
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x7ad8c2…e7d078
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0xde7726…6ccd87
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0xd569aa…027781
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x640742…a8466f
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x0faa28…945f6f
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0x108710…f9bbc4
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0xc29052…e87045
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa9d ago0xa6459b…95529a
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0x621d16…097c0a
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xefea9f…a7d5a7
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xf6b36c…192fb0
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xab9353…066f47
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xbc559d…c9ec0f
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xcc1a21…04df14
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xbf6e96…5533c7
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xca4e0c…d48c40
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0x4553ec…865d2c
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xe7317c…dd4ad2
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0x4ba068…c15c2d
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0x8c171c…c01337
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0xba2559…c9d737
0xa361…cab10xfe80…47eeBaseBase$0.001100%fluxa10d ago0x19230e…506b27

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

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

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: 0xa361…cab1

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