AgentReport

0x7f34…dabc

0x7f342c44a86354cea1323d9918c970b3e0c4dabcExplorer
Paid out
$34.32
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21606
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.32 of the $261.27M Roundhouse has indexed across 717,316 wallets — less than 0.0001% of it.

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

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%$3.791,0002

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 21,606 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.30$0.00851225d agoGraph
0x8324…fd0e$1.49$0.00149238d agoGraph

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

Data quality

61% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x8b5c02…f6b88e
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x24ec32…27ddbf
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x7d65dd…de846a
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x5a3bd4…840f69
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x2f5790…f0544a
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x109bf8…b3ffbd
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x723aae…2b350c
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x4d46de…8af00e
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x805b3b…b8461f
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x8f7896…fade02
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x09452a…691bfe
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xbb99c2…6c7c30
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xb5de9c…c3d59e
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xa6cb51…d0f5ce
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x2e964a…fdde41
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xc3c4e0…75eb91
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xb669f6…acf60e
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xcdc3ab…ed1252
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x8967ad…7c347e
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0xee8afd…6fc024
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x6cd967…9f15cc
0x7f34…dabc0x0495…eed9Base$0.01100%payAI225d ago0xe7c21a…02db37
0x7f34…dabc0x0495…eed9Base$0.10100%payAI225d ago0x10e01b…2e0391
0x7f34…dabc0x0495…eed9Base$0.01100%payAI225d ago0xff387a…8e994b
0x7f34…dabc0x0495…eed9Base$0.0001100%payAI238d ago0x971c1f…eb4a3a

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

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

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: 0x7f34…dabc

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