AgentReport

0x217e…9916

0x217e9cea6cf3222f074b85436063400cf64a9916Explorer
Paid out
$2.98↑ 79%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2978↑ 79%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $2.98 of the $3061.41M Roundhouse has indexed across 1,398,817 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 11m ago
    $0.77
    767 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 114d ago
    $0.23
    233 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 2,978 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.77$0.0076711m agoGraph
0x9c95…e299$0.23$0.00233114d agoGraph

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

Data quality

77% 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
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa20h ago0xfa0ade…c6fc90
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa20h ago0xad4d1e…75ed2c
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa21h ago0x740052…46c692
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa21h ago0xb533e2…e04c4f
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa21h ago0xa3aa7f…93addc
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa22h ago0x6d5e66…c4cc81
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa22h ago0x8d11b6…c82104
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa23h ago0x8b754e…42ca06
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa23h ago0x49ffea…83b3f7
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa23h ago0xdd45f6…7bccf0
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0xe1a5cd…e1b04a
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0xb48afc…3b32ff
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0xaeeabc…c8c8cc
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0xaf24d5…fa265b
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x213648…8daff4
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x485dfc…422351
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0xaace3b…3d6fcf
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x91ce45…c9e8d7
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x709faf…e6b321
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x3f6deb…4191f2
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x48869f…e1f585
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x59fd03…1a18de
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x89b487…96792c
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x568f86…74b29e
0x217e…99160xfe80…47eeBaseBase$0.001100%fluxa1d ago0x68780a…4364dd

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

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

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: 0x217e…9916

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