AgentReport

0xd299…0bdf

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

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    264 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.00264277d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams343d ago0xbefb01…303c72
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams343d ago0x21b8fb…83f6a7
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0xeee4f0…f5ea01
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0x6353cc…4aa7a5
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0xee656a…73231b
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa79679…7c0f91
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0x5caa76…17453c
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0xad0c4a…18391c
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0x97c0c8…6ede88
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0x6a0808…ce366f
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0x84702b…681a33
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa6caad…8435a3
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc48f44…1820aa
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams344d ago0x457a3a…6423b4
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8578b…de6d06
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0x70a26f…71e8c7
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0x6a40e3…2364ec
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0xda4bca…494b43
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0x0b7b32…5648df
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0x4f626c…da6188
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0xf51312…c901fe
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0x300c6d…7e7cd1
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0xacb2ac…f3199a
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc6cb01…ebd79c
0xd299…0bdf0x6482…b779BaseBase$0.0001100%daydreams345d ago0x63b367…44e869

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

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

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: 0xd299…0bdf

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