AgentReport

0xef31…b176

0xef31df60c63f6b84b42dcc50eda7d314c078b176Explorer
Paid out
$1.22
Last 7d vs prior 7d
Received
$1.21
Last 7d vs prior 7d
Settlements
377
Last 7d vs prior 7d
19
Distinct counterparties
Over the whole indexed history

Paid $1.22 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.

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

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

$1.22 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.

  • 0x3577…ca8d · last paid 36d ago
    $1.22
    1 call

    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
0x3577…ca8d$1.22$0.00136d agoGraph
0x8095…423c$0.00$1.08217340d agoGraph
0x76e5…1025$0.00$0.043393d agoGraph
0xacc8…de13$0.00$0.0123374d agoGraph
0xe1dd…3a0b$0.00$0.0113374d agoGraph
0xf273…8383$0.00$0.0110374d agoGraph
0x50c0…4ccd$0.00$0.00904515377d agoGraph
0xe0e3…d80d$0.00$0.00844215377d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 377 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2c6d…c5490xef31…b176BaseBase$0.000422100%questflow374d ago0x1169e2…e5c81a
0x2c6d…c5490xef31…b176BaseBase$0.000391100%questflow374d ago0xee0122…0921cc
0x2c6d…c5490xef31…b176BaseBase$0.000536100%questflow374d ago0x57ef43…21d433
0x2c6d…c5490xef31…b176BaseBase$0.000314100%questflow374d ago0xdda4fa…0ed16d
0x2c6d…c5490xef31…b176BaseBase$0.000242100%questflow374d ago0x57b655…53698a
0x2c6d…c5490xef31…b176BaseBase$0.000188100%questflow374d ago0x697301…95f552
0x2c6d…c5490xef31…b176BaseBase$0.000516100%questflow374d ago0x694a62…8c843a
0x2c6d…c5490xef31…b176BaseBase$0.000552100%questflow374d ago0xb618be…305d97
0x2c6d…c5490xef31…b176BaseBase$0.000256100%questflow374d ago0xbbfaa4…45ec2d
0x2c6d…c5490xef31…b176BaseBase$0.000184100%questflow374d ago0xcbec8e…55f56a
0xbad0…71f00xef31…b176BaseBase$0.001008100%questflow374d ago0x3cbc35…eb6583
0xbad0…71f00xef31…b176BaseBase$0.000712100%questflow374d ago0x6a9512…39b9c7
0xbad0…71f00xef31…b176BaseBase$0.000683100%questflow374d ago0x9b5adc…e10dba
0xbad0…71f00xef31…b176BaseBase$0.000829100%questflow374d ago0xa6d65a…3e5e43
0xbad0…71f00xef31…b176BaseBase$0.001063100%questflow374d ago0x4c818e…5d4e0d
0xbad0…71f00xef31…b176BaseBase$0.000692100%questflow374d ago0x47da7a…e1a5fd
0xbad0…71f00xef31…b176BaseBase$0.000556100%questflow374d ago0xa15e2a…44d995
0xbad0…71f00xef31…b176BaseBase$0.000325100%questflow374d ago0x76ae97…2b0912
0xbad0…71f00xef31…b176BaseBase$0.000297100%questflow374d ago0x84c457…c2be7f
0xbad0…71f00xef31…b176BaseBase$0.000238100%questflow374d ago0x0943df…ad0c55
0xbad0…71f00xef31…b176BaseBase$0.000224100%questflow374d ago0x4b0583…47f6b2
0xbad0…71f00xef31…b176BaseBase$0.000583100%questflow374d ago0xf191d2…febdcb
0xacc8…de130xef31…b176BaseBase$0.000801100%questflow374d ago0x54778f…ee8c8e
0xacc8…de130xef31…b176BaseBase$0.000537100%questflow374d ago0x24007f…b7c98c
0xacc8…de130xef31…b176BaseBase$0.000481100%questflow374d ago0x703d59…5118d9

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

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

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: 0xef31…b176

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