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 $3068.58M Roundhouse has indexed across 1,402,563 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%daydreams324d ago0xed3b31…7d2368
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0xec280b…deb785
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0x013eda…37f14b
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0xc100a3…67f08b
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0xe0e297…02427d
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0x55f45a…1a4075
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0x64c968…283646
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0x62adb4…1395d7
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0xa78ee0…44548c
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams324d ago0x67a7d2…4fcf1a
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0xe73ad0…e4e1eb
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x725c53…1359ce
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0xcf239c…9f2b7f
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x022639…4d4da4
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x9ca2a2…280431
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0xd6d0cd…982553
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x2a3df2…dd55d6
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0xc91a76…29e48f
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x2cb239…5e2338
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x51eace…359069
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x48ed97…f0f34d
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams325d ago0x9a8d0e…646806
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams326d ago0xe619ef…133491
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams326d ago0xaa1b94…5e0f3a
0x7170…2e210x6482…b779BaseBase$0.0001100%daydreams326d ago0x5d9f2c…4bc4b5

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.