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%daydreams344d ago0xa04d38…e0bfd6
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x94146e…a9e766
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3d096e…d53ba3
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x9856f5…2f84b3
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x7fbdc1…d2b184
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa35aa1…8948c2
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x309820…526f8c
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x4121ee…6eaf80
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa5601d…7108d1
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0x564b32…c6d418
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa44c71…dc045f
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0x4feec9…e10fdc
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa1cb7c…6b6b17
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0x9ab7c4…56bbd6
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0x0e7e0a…0d280d
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0xd58945…75daac
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe845a9…b38c87
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0xcba7bd…308b09
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0xcceef3…a93d70
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0x49c68c…6b3347
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0x9d7fc2…8207a2
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb7fa62…7b4140
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0c4db1…8c9269
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams346d ago0x651ee2…c87fb4
0x5879…816c0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0cb0e0…5dfdf5

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.