AgentReport

0x1fc3…0027

0x1fc3fdb7e5983c3d6a1a2fc21b79e07f83b70027Explorer
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 $3068.58M Roundhouse has indexed across 1,402,722 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
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams326d ago0x4cf727…08c39e
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams326d ago0x5198f6…5ede15
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x9525a6…45b75a
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x450a43…9c3051
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x240f18…17f584
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x632248…bde639
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x8e7386…4139cc
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0xe18cdf…4ecbd5
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x2336cc…b9d3e3
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x7c04ef…77f7a2
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x9e8257…bc0f5a
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams327d ago0x1e4012…a9b2b8
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams328d ago0xf128ee…f1efff
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams328d ago0x33cf9c…ff6a9a
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams328d ago0xb1971d…65e1ea
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams328d ago0xa898aa…936c63
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams328d ago0x708808…1c2d53
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams328d ago0xddce3a…7420b1
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams336d ago0xc1a0e2…d17fdf
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams336d ago0x5053d0…830278
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams337d ago0x575256…d2636d
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams337d ago0xcd6322…75e2c9
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams337d ago0xddd324…104895
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams338d ago0x908a89…dde815
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams338d ago0x3fc1d2…f2e648

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

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

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: 0x1fc3…0027

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