AgentReport

0xdd99…e66f

0xdd995add70c86495816435b923a1aa882657e66fExplorer
$2,000.00
Paid out
$0.00
Received
2
Settlements
2
Distinct counterparties
In the 2 settlements scanned

Paid $2,000.00 of the $833.87M Roundhouse has indexed across 1,300,188 wallets — 0.0002% of it.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

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 catalogue100%$2,000.0022

$2,000.00 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.

  • 0xfd78…d002 · last paid 12h ago
    $1,990.00
    1 call

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

  • 0x09ae…ec64 · last paid 12h ago
    $10.00
    1 call

    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…

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfd78…d002$1,990.00$0.00112h agoGraph
0x09ae…ec64$10.00$0.00112h 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, in all 2 observed settlements.

Organic volume $2,000.00 of $2,000.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xdd99…e66f0xfd78…d002Base$1,990.0070%0x07ae…0e6712h ago0x246a8e…180d9f
0xdd99…e66f0x09ae…ec64Base$10.0070%0xc99d…a8f412h ago0x579b1f…a74d60

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

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

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: 0xdd99…e66f

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