AgentReport

0x287c…58f5

0x287cb11500d7a0c253b126e5567e88f903aa58f5Explorer
Paid out
$8,000.00
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $8.00K of $3.31B indexed (0.0002%).

Chains (from the recent scan): Ethereum (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%$8,000.0022

$8,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.

  • 0x6e56…8ce2 · last paid 248d ago
    $6,139.53
    1 call

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

  • 0x1326…1710 · last paid 320d ago
    $1,860.47
    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…

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
0x6e56…8ce2$6,139.53$0.001248d agoGraph
0x1326…1710$1,860.47$0.001320d agoGraph

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

Data quality

77% of volume with one counterparty.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x287c…58f50x6e56…8ce2EthereumEthereum$6,139.5370%0xbfa1…1b33248d ago0x48cce4…3106ee
0x287c…58f50x1326…1710EthereumEthereum$1,860.4770%0xbfa1…1b33320d ago0x9c83e3…154aec

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

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

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: 0x287c…58f5

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