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%fluxa66d ago0xf0359e…7fb035
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xcd189e…558426
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe52e84…a63498
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x161aed…4e7afb
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x668616…352498
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd68e6e…352ca0
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6be2fe…24cf8e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0decfd…29af72
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x3a0d04…98f412
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x2d846a…b57804
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5ae975…95f4c7
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5bb5e3…b57fd0
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe3a975…83bc09
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf46a26…48fc60
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x987bd3…419e14
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xb53f3a…b75196
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xbb45ca…a47b3e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xa2ca3f…068d32
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x286c70…b07bca
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x59e266…395295
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x3859ad…d5d207
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x066608…9a9a4e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0xa99e05…4cae7c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x1becb1…795306
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa66d ago0x018497…23f24d

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.