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%daydreams341d ago0x0dde44…fedd26
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams341d ago0x13ad2d…64a3f7
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams341d ago0x0a2984…fcb35c
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams341d ago0x84b8dc…d6217e
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams341d ago0x5d42e2…244447
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0xd82c6b…da349c
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0x18bfb7…f87a67
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0x6bdb19…d5fe3e
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0x65aabb…6a1692
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0xb57b5a…5506a3
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0xdc90fd…8f42fd
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0xddd75c…21dbe7
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0x8fe321…391ed1
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0xc81aba…4adfe7
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0x7c98d4…c1e7a1
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams342d ago0x5532b1…298828
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0xa4923f…79d05e
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0x33cd0f…ca67f4
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0x4246fb…88af82
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0xd12eb4…9c5cd7
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0x4bc502…0ca811
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0xa11ea8…034445
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0xaa68e7…fe9e45
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0x9e2fc9…78a44c
0x8f27…16940x6482…b779BaseBase$0.0001100%daydreams343d ago0x719ec2…9a9321

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.