AgentReport

0xe771…ac0b

0xe771c8cc43d93f337300b00b1d5e31e530efac0bExplorer
Paid out
$1.01
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
1013
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.01 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.

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

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.001,0002

$1.00 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 38d ago
    $0.85
    846 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.15
    154 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Folded from this wallet's 1,000 most recent settlements of 1,013 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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.85$0.0084638d agoGraph
0x9c95…e299$0.15$0.0015477d agoGraph

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

Data quality

85% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xf76af5…6cb449
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x9833d4…334674
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x2e502e…9bd6d9
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xcd03d1…8e1cb1
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x9f56a7…80bcee
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x0c0f99…e899be
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x067605…1c1ccf
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4c5637…ad6224
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x3b8a79…4bcc3b
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x88ddac…c133de
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xa9f438…13b07d
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x487461…8c2f29
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xc93382…fc7212
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x7ebd36…1d8479
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe1ba75…e99813
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x76fe7c…ad0173
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x8d1c4c…69b624
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xefac46…edb4ea
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x65199a…47cd5a
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x525b2c…f3000d
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x529ffc…400650
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x05dff9…7dab2d
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x14ae54…16609f
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xb24569…56100b
0xe771…ac0b0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x155b11…46c9fd

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

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

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: 0xe771…ac0b

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