AgentReport

0x270c…f730

0x270c9a2c67f116d36346bae82cb34f12dc03f730Explorer
Paid out
$1,232.30
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1,232.30 of the $3217.31M Roundhouse has indexed across 1,445,802 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (5)

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%$1,232.3052

$1,232.30 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.

  • 0x5c7b…35c5 · last paid 19d ago
    $882.30
    4 calls

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

  • 0x6769…83c5 · last paid 116d ago
    $350.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…

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
0x5c7b…35c5$882.30$0.00419d agoGraph
0x6769…83c5$350.00$0.001116d agoGraph

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

Data quality

72% of observed volume is with a single counterparty, in all 5 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x270c…f7300x5c7b…35c5EthereumEthereum$112.3070%0xc10a…ae5d19d ago0x4d22c6…c30f9a
0x270c…f7300x5c7b…35c5EthereumEthereum$130.0070%0xd016…b67a19d ago0xf30c71…7c074f
0x270c…f7300x5c7b…35c5EthereumEthereum$320.0070%0xd016…b67a50d ago0x3e0222…8134e8
0x270c…f7300x5c7b…35c5EthereumEthereum$320.0070%0xe459…e4de80d ago0x775e8b…bde661
0x270c…f7300x6769…83c5EthereumEthereum$350.0070%0xe459…e4de116d ago0x2ab403…1de132

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

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

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: 0x270c…f730

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