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%daydreams338d ago0x9b17fd…577813
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x24ce3f…b8670d
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x60ea06…5026fa
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams338d ago0xe4ca29…0bcddc
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x73f136…7d3b1e
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x971fa2…cc31ab
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x837439…480348
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x66b11a…fcf1ae
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xad22d6…ae7452
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x918ccd…60ce02
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x75ef0d…92ccd2
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x5a45ad…3eaccb
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xac7d21…aa09a0
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb82907…e1a62a
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x95da98…2a3d31
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc883b4…e7fed4
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x048bc4…d5b9ab
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3bd6c4…c9e8b3
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6a6d96…15039a
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6c314e…2471b6
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa3e9dc…49d5dd
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xe5a568…24611e
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2e9d10…3e4764
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x1658b5…c89517
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xbab254…71d77a

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.