AgentReport

0x270f…ce6c

0x270f76bb3902128644f732d470caa5a3e8e4ce6cExplorer
$0.02
Paid out
$0.00
Received
2
Settlements
2
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $258.47M Roundhouse has indexed across 713,069 walletsless 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 catalogue59%$0.0111
Web & Content41%$0.00711

$0.01 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.

  • 0x9d84…153a · last paid 64d ago
    $0.01
    1 call

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

  • Exaapi.exa.aiWeb search?Endpoint up
    0x6d6e…9192 · last paid 64d ago
    $0.007
    1 call
    2 of 3 catalogued endpoints list a price this agent paid
Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x9d84…153a$0.01$0.00164d agoGraph
0x6d6e…9192$0.007$0.00164d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x270f…ce6c0x9d84…153aBase$0.01100%0x2aef…963364d ago0x721049…20753c
0x270f…ce6c0x6d6e…9192Base$0.007100%coinbase64d ago0x875949…ff9018

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

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

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: 0x270f…ce6c

curl -s 'https://api.roundhouseai.io/v0/agents/0x270f76bb3902128644f732d470caa5a3e8e4ce6c'
curl -s 'https://api.roundhouseai.io/v0/entities/0x270f76bb3902128644f732d470caa5a3e8e4ce6c/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.