AgentReport

0x458a…0ebd

0x458af8f3dad66a6f9f195a22ce2dd73a80170ebdExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
266
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (266)

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.032661

$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
    266 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.00266276d 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 266 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xd50f1c…00a190
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x0e6beb…809884
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x5f36f5…c64d06
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa38e68…33fb3b
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x083588…28038f
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x37b6b7…70224e
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xd2c3f6…354516
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x44774d…67e607
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x6920b6…cf4807
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x1b4cb6…35a1c4
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x68d20e…edae18
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x55e846…88e50b
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc456f7…98ad3a
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x6ceb86…d91159
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xf713f9…03bee5
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x5408d5…06cc07
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe53119…7ec838
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x298ff2…a4dfe8
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe617b1…8418e6
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xbc54c0…a17128
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x8bf2b3…afb4c0
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x8ea6fd…7d064b
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x13153d…3acdc5
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0aca31…e5da8d
0x458a…0ebd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x272eae…36f413

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

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

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: 0x458a…0ebd

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