AgentReport

0x7170…2e21

0x71707b820384751e5a30b1e3d1af6cc2788c2e21Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
256
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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.032561

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

  • 0x6482…b779 · last paid 277d ago
    $0.03
    256 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
0x6482…b779$0.03$0.00256277d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0x8b8b7c…86fdd3
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0x65bb26…7ded8e
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0xe49e28…83a45d
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0x9ac94b…35860c
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0x73b730…a8f29d
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0xa37c13…2d62e9
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0x2dadfa…fb9ad3
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0xb7fc11…0daa06
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams342d ago0x78c5a0…3e4f81
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0x1f1ed0…cf9436
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0x27be90…0f26f1
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0xf24951…d779af
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0x77a9a2…aa5e9c
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0xa86465…abb90c
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0xa0e41c…6c6744
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0x7f2cf7…d9cc0f
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0xca6f12…e7a878
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams343d ago0xaeec9c…fb7dae
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0xe0f411…605381
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0x2bb776…091d52
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0x2fdd5e…668cea
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0xedc160…b978f3
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0xf4093d…dcd693
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0xb4a738…c82d90
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams344d ago0x343753…324993

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

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

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: 0x7170…2e21

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