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,861 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%fluxa67d ago0x9d4cc5…17cdeb
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xb0ead7…82462b
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xe58fd0…9f2fb2
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x3bd7fa…0e189f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x366019…015ad0
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xc39d56…8ce0bb
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x66946b…a3d10e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x72c45a…67a91c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x0bf03f…9f05fd
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xba17eb…bd2aab
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xbdce55…257d79
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x040240…005ffe
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x78bbc0…ac092a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xd7abde…dc1c58
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x60dea8…5b9391
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x36f50f…804274
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x5d7d41…80c47c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x2873f0…33ffd7
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x548301…be4a1e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x51a639…bd0127
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xf5347f…fc0f3f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0x9bc7ed…488cd6
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa67d ago0xdb4d16…b1050f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc280bd…8148f1
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa68d ago0xfede53…1cbb86

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.