AgentReport

0x7d4f…f761

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,367 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    259 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.00259276d 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 259 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams352d ago0x392be0…7b953f
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9d217…7eea39
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams352d ago0xa31cfc…8e2f9d
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams352d ago0x193fba…0eec3c
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams352d ago0x091f6f…ac8fdb
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams353d ago0x23f8a3…b7022c
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams353d ago0xb17942…56dd32
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams353d ago0x865fdf…94751e
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams353d ago0x696efe…299dc9
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams353d ago0x9db556…3dc237
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams355d ago0x346807…7ed015
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams355d ago0x5b7ce4…215633
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams355d ago0x8abc35…4975e0
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams355d ago0x5c6084…413580
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams356d ago0x24d221…7e7f5d
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams356d ago0x18224f…45af40
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams357d ago0x396f9b…8996b4
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams357d ago0x6d551e…b13004
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams357d ago0xe5314b…c7be45
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams357d ago0xa544bf…ec9038
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams357d ago0x5c06ff…2c6081
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams358d ago0xef953d…8608c9
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams358d ago0xc9d018…6bfa54
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams358d ago0xbd12b6…a12f08
0x7d4f…f7610x6482…b779BaseBase$0.0001100%daydreams359d ago0x450742…c0de7e

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

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

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: 0x7d4f…f761

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