AgentReport

0x200d…d975

0x200df1cd221d78862b913b46a2183bdbe4aad975Explorer
Paid out
$0.61↓ 67%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
609↓ 67%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.61 of the $813.26M Roundhouse has indexed across 1,055,948 wallets — less than 0.0001% of it.

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

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

$0.61 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.

  • 0xfe80…47ee · last paid 6d ago
    $0.53
    527 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 45d ago
    $0.08
    82 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

AprMayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfe80…47ee$0.53$0.005276d agoGraph
0x9c95…e299$0.08$0.008245d agoGraph

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

Data quality

87% of observed volume is with a single counterparty, in all 609 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x200d…d9750xfe80…47eeBase$0.001100%fluxa6d ago0x495d6b…988a0a
0x200d…d9750xfe80…47eeBase$0.001100%fluxa7d ago0x0c2556…f39658
0x200d…d9750xfe80…47eeBase$0.001100%fluxa8d ago0x850cef…6d6579
0x200d…d9750xfe80…47eeBase$0.001100%fluxa9d ago0x0fb760…b3b642
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0xd0f3f6…d76169
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x398a9f…baa9ec
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x6554c1…e8e1a3
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0xb5952e…567e08
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x6443fd…8c4311
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x1f93dc…4861e4
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x459389…8fd9b3
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x34b18c…4e7da3
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x474fe1…015f63
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x59a65b…8ad454
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0x930893…9c73bd
0x200d…d9750xfe80…47eeBase$0.001100%fluxa15d ago0xc3b48d…3ba71b
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0x17fabd…98b268
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0x837b47…ecb2ea
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0xa17378…f9d21b
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0xfbc6a3…74ca24
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0xad6103…342cc2
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0x7b0bbe…374067
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0x663951…eb16d4
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0x689544…ea6766
0x200d…d9750xfe80…47eeBase$0.001100%fluxa19d ago0xdb7ec0…2f65c9

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

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

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: 0x200d…d975

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