AgentReport

0xa133…ce44

0xa133f144bc35542b49a2558915d1bf5ff51fce44Explorer
Paid out
$0.96
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
961
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.96 of the $3060.46M Roundhouse has indexed across 1,397,991 wallets — less than 0.0001% of it.

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

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%$0.969612

$0.96 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 65d ago
    $0.60
    598 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 76d ago
    $0.36
    363 calls

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

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.60$0.0059865d agoGraph
0x9c95…e299$0.36$0.0036376d agoGraph

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

Data quality

62% of observed volume is with a single counterparty, in all 961 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xab6467…e52a15
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x890fc4…259094
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xeecd5b…08a10f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xe62167…9a8921
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x4e3bea…744446
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xcb1f98…b153dd
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa4a9a1…2cb2d9
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x85903d…ff64cb
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x527fdd…a5bb9a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x915933…edf4b7
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x8f7151…aa867f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xc19498…016234
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x319021…b763a9
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x170fbf…ecd2c1
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd42729…75517e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x520e3e…43c49f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x8095b6…cde8f0
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0xb34393…d04792
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x002c24…26e8da
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa69d ago0x455a9b…e671f9
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa70d ago0x68d6fb…66d7dd
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa70d ago0x0a092d…4a664a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa70d ago0x7d0c95…186f1c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa70d ago0x3a8852…a3aa62
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa70d ago0x5b4d00…714b24

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

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

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: 0xa133…ce44

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