AgentReport

0x5879…816c

0x587906dcee976fd91c1ee8603eb4fc1fceef816cExplorer
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.84M Roundhouse has indexed across 1,402,228 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
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbf6306…4b1621
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa4061c…3c7990
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0xea945c…6a3921
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7c8c3f…b597af
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0xec9530…ca21fd
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0x670f07…4801ff
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9ab69b…ded649
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams354d ago0xc4240e…f7d6bc
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams355d ago0x501fbc…df530d
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams355d ago0xcae5db…e1dcd7
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams356d ago0x13b92a…e77467
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams356d ago0x84b18d…2c4be3
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams356d ago0xe403fc…3187d9
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams357d ago0xdc6e88…30bbc6
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams357d ago0xe31214…b7ecdf
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams357d ago0x64341c…35dfc2
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams358d ago0x619c0f…3382fc
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams358d ago0x08633e…832d37
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams359d ago0x394cc7…60afe4
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams359d ago0x9baa83…a0e233
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams359d ago0xff0dcf…8c6073
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams359d ago0xdb59de…dfa3c5
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams359d ago0x96165c…b6093a
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams360d ago0xd4fd7f…873e66
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams360d ago0xa93b49…a56d52

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

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

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: 0x5879…816c

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