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%daydreams326d ago0x7b4b8e…5ab485
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xfbae47…606ce5
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0x616dee…2fb122
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xaabb3c…cc3a86
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xbc2312…60d191
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xecab23…e99c8e
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0x9e83ad…129b18
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd51d74…229541
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xdb8a02…3bbc22
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xab749d…17b3d2
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd67337…b17e36
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams327d ago0x09d2c2…9c9ab8
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf4ebb5…abda60
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams327d ago0x99c242…ecc7d8
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams327d ago0x5f9aaf…d7c546
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams328d ago0x2066d8…9d6c69
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams328d ago0xf130b3…0d50f3
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams328d ago0x48353c…373266
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams328d ago0x6a0f91…376237
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams335d ago0x4d52fd…4185cf
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbdc732…875cdb
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams337d ago0x6c0e3a…aea54b
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbe6fa8…8aff7b
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams337d ago0x73d701…34571b
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams337d ago0xb310c5…a0d0af

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.