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%daydreams343d ago0x739ab0…9f1030
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0x9148fb…1c2662
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0xf214dd…c2d72f
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0x017a79…d026ff
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0x3bbd7c…062400
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0x2cf070…279560
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0x1dd002…479110
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0xc16654…871790
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0xfb6ee6…f46e37
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0xb430b1…edd948
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams344d ago0xbc7f7a…c66f4e
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0x3c6a65…b3ad0a
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0xc1f969…a9d205
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0xbeb16c…02871e
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0xc136b4…9e1860
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0x1b4a71…4bdcaa
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0x352119…88b601
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0xf9ac75…dfb6ca
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0x36db82…96f4cd
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0x091cef…5cbf0f
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0xcd85e0…0e5148
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0x1c16a2…ae6ffa
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams345d ago0xdf6620…2c35b1
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x5f7184…726c76
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams346d ago0x1a5d48…0346df

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.