AgentReport

0xa363…9d1f

0xa3631ca00163902b40be36c7ef32812a3fc29d1fExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
252
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (252)

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

$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 276d ago
    $0.03
    252 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.00252276d 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 252 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x6b405b…c1aaa7
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xd050df…db8947
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x542de8…b995de
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x756690…b7e95a
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xd87bda…fcb642
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xebe5bc…475ba7
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xd6ef3f…7a63f4
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x20043b…6d4b0b
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xeee19b…134bbe
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xcb39d8…1a2ac0
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x82a8b6…f67fe8
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xc8c6a4…f8e1b2
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x2fde36…9fcf36
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x4d5c0c…6aaa5c
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x71e0fa…842d41
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x3eceff…bc9a8f
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xf43940…ecc7ba
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xa6038e…5653c2
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x4618ee…e5f930
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x390af5…895f91
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xc4f86a…e3de99
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xe85e0b…01a576
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x8b331d…5a0de6
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x36c579…9bc46c
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x322087…8ae805

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

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

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: 0xa363…9d1f

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