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%daydreams326d ago0x563f62…a863e0
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x148152…a46791
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe2a50d…9bd99d
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x3d3a7c…ecf1cb
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x41dc58…f28053
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x98cff2…b10898
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xf5532c…c59595
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x4e4200…d6ad9a
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x4b4ed7…5cb636
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x030e8f…d3feab
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x977fe3…f48f45
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x07e946…70d546
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xc65d1b…de1f19
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x12dead…217bab
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x7b03a5…63e8ec
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x54e16c…213ad8
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x9e6668…1d885c
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams328d ago0xece91e…0d8387
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams328d ago0x23ae12…107a9f
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams335d ago0xd8dc3c…ae23e0
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x9ca611…81ca73
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x394147…ded157
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xb8e703…839af9
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x241177…1dbd00
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf2f218…eac5c6

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.