AgentReport

0x8f27…1694

0x8f271dace7bddaef4109bd549437dbb499611694Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
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 (261)

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

$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
    261 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.00261277d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0xba2dd0…760e3b
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0xe11a9b…8a5385
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x142639…a1cf1d
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x6f08a7…af788c
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x778581…8766ee
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0xdc7b82…e54de1
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0xd8da79…1ffbfc
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x1c1a38…4af2dc
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x3e9ea4…5b7c50
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0x9338e0…3d89b1
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0xf6799f…8a356f
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0x139e6c…8b579a
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0x82d49d…c0b709
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0xc2c6ce…8271e3
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0x2c5b0e…99be82
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams347d ago0x7e4f48…7836e5
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0xae8a3e…9bb93a
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0x4f0f62…7a1bde
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0x1c771d…99f4c3
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0x236e86…97236a
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0x03e1db…b79e07
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0x5254b5…17ba2e
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0xa8366e…28781c
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0xd945d7…80aeec
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams348d ago0x2f411c…b1d621

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

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

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: 0x8f27…1694

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