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,401,919 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%daydreams338d ago0xf71a3e…40a5c5
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams338d ago0xce6ed8…00adae
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams338d ago0x1d46be…f699cd
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams338d ago0xe0d753…ef2137
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams338d ago0x5d7213…7ec996
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams339d ago0x2cc793…1399e0
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams339d ago0x07f0a4…e7784f
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams339d ago0xcdde61…464f2e
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd3b59e…903f69
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0xda07ee…1cf659
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa66f42…3a9507
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6d3fb0…f1ebc0
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0xad84b4…a1ce2a
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x5c5462…7f2635
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x78e7ff…9cccbc
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x93fb92…2927cf
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1d9607…38ed66
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x300e9b…84e0e2
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams340d ago0x63fb8a…ccbb20
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams341d ago0x6dc7e4…509309
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams341d ago0xac4d42…772c70
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams341d ago0xebc578…f91507
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams341d ago0xf3896f…042428
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams341d ago0xfc991f…045efc
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams341d ago0xbff5c6…542099

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.