AgentReport

0xa184…f8a5

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

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

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

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

$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
    265 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.00265276d 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 265 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams343d ago0x80eaa5…6cd717
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams343d ago0x5c9e0e…b5e47f
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams343d ago0xf80a0e…a103d7
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x1087c9…6f69aa
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x30bb17…25ad03
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x954b45…46f296
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x875077…286382
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x062a07…96bb22
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x633e70…eb9c36
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0xc16331…3fa571
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0xbefa2a…f2462d
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x599a4a…557046
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0x9168a2…35b44b
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams344d ago0xf0bcf9…18fc80
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x2f1c1b…8ed00e
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x5305a6…37a6ad
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0xd9e9da…1bb255
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x0bc378…35f3ce
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x3f9a98…40df1d
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x78531a…39155b
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x48ca40…e4948f
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0xb2c1e8…f96c27
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0x1b6827…35688e
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0xa8b8c0…17d40c
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams345d ago0xbd80d3…dcf3d4

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

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

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: 0xa184…f8a5

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