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,398,118 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 77d 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.0036377d 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%fluxa71d ago0x01c33f…fb1ae1
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0xa6025a…614916
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0x14b7b3…88ffa2
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0xf51191…642b4f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0xffc9ce…219f66
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0xab3277…807239
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0xee9973…578d3f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0x8e7d5f…824728
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0xd95d9c…1ad7f7
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa71d ago0x910135…6c5d8a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x37b6b4…a73d26
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x5b983c…c1ac60
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0xe1e424…a1ffef
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x0729c1…ce608b
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x24993f…bcc7c5
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0xdf306f…117660
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x0c5e4c…dc6aad
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x88b04d…22d629
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0xb8e448…c90b55
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x61500e…8ca974
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x44348a…903bb6
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x53afca…35ad6a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x8140a0…a85e05
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0xc8dd64…d24bbe
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa72d ago0x970916…fc893f

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.