AgentReport

0x6eef…dd9d

0x6eef333873dc262f817c959a2b4ed74e3befdd9dExplorer
$0.006
Paid out
$0.00
Received
2
Settlements
2
Distinct counterparties
Over the whole indexed history

Paid $0.006 of the $3053.48M Roundhouse has indexed across 1,395,363 wallets — less than 0.0001% of it.

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

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 catalogue83%$0.00511
Location & Weather17%$0.00111

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x110c…b784$0.005$0.0013h agoGraph
0xd6fc…fb0a$0.001$0.0014h agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

83% of observed volume is with a single counterparty, in all 2 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6eef…dd9d0x110c…b784BaseBase$0.005100%coinbase3h ago0xede7dd…5ebf64
0x6eef…dd9d0xd6fc…fb0aBaseBase$0.001100%coinbase4h ago0x43e6c7…987432

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

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

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: 0x6eef…dd9d

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