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,402,228 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%daydreams352d ago0xe3464c…2c3857
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0x9107e0…4f7cfb
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0xaaba9c…a61f96
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0x61d517…5ca87e
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0xaa395a…f6464a
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0x2ee552…629dad
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0x12fd5a…0b924b
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams353d ago0x8c52d7…123ff8
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams354d ago0x871871…f55e6c
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams355d ago0x11f5d3…7e545f
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams355d ago0x2c6b13…d38e43
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams355d ago0x5ba08a…6d19f6
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams355d ago0x189659…cc6703
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams356d ago0x62faec…794898
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams356d ago0xce09b2…ba046a
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams356d ago0x49538e…b01667
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams357d ago0x71b1db…7931df
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams357d ago0xf90d7c…e83f68
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams357d ago0x4c01c0…445a4c
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams357d ago0xc3944d…4e1423
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams357d ago0xc37665…a5cfb9
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams357d ago0xae2729…bd8f64
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams358d ago0xf2ec3e…64542e
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams358d ago0xd8f704…654762
0xa184…f8a50x6482…b779BaseBase$0.0001100%daydreams358d ago0xa62a9d…04eef7

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.