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 $3061.41M Roundhouse has indexed across 1,398,256 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%fluxa73d ago0x2ea8e0…e4acda
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x57c361…83cab0
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xc9df09…57e08c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x356146…b504b7
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x5d2bb9…af2189
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x528264…869d02
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x08137d…3c4f8a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x68f0b3…6eaa45
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x6f69cd…2d1eab
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xb87512…935135
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x6fc646…d2408e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xc708a2…797f2f
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x150e02…b3cc0c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x72fb46…39672c
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x19558c…f7ca17
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x88d937…b3782e
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x54ea52…5a3137
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x926dfa…7411a2
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xc96c86…1b4225
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xaaf47c…8afa4a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x980310…0fc42b
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0x92040c…f8201a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xb34827…bdb8da
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xcb1313…6f742a
0xa133…ce440xfe80…47eeBaseBase$0.001100%fluxa73d ago0xc3503e…23f283

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.