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 $3070.29M Roundhouse has indexed across 1,403,290 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%daydreams349d ago0x78583b…e66ca5
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams349d ago0x300de4…faa2c9
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams349d ago0x5e6b2a…15e0af
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams349d ago0x1f88f8…dc5045
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams349d ago0x14beb0…3adb64
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams350d ago0xca94cf…26e03f
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams350d ago0xdd6830…ba83b2
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams350d ago0xc8d55f…5704e2
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams350d ago0x5760a1…62f49c
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams350d ago0x06b4b0…b5d4f8
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0x7543d9…51247a
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0x9467bd…fc2d63
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0x9cdcdb…d849d3
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0x0ed501…e27275
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0x2c9286…7009dc
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0xc590d8…c4f4e6
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams351d ago0xe45045…2baf53
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0x320668…be30da
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0x096a92…9b16d2
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0x682b77…a3f52b
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0x2dcfef…70212f
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0xca2e6d…66ab0a
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0x06ce17…6d7699
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0xece846…02193a
0x1fc3…00270x6482…b779BaseBase$0.0001100%daydreams352d ago0x812b83…e9ea19

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.