AgentReport

0xf629…eaf1

0xf629f19cbefee1ff891d1d807bdde98b4050eaf1Explorer
Paid out
$34.47
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21561
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.47 of the $261.41M Roundhouse has indexed across 717,464 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.771,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,561 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.29$0.00852226d agoGraph
0x8324…fd0e$1.48$0.00148239d 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
0xf629…eaf10x0495…eed9Base$0.01100%payAI226d ago0x480509…241cbb
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x9dca83…456d9f
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x7c189b…c0f113
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x081007…21c509
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x020f71…763c32
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0xf53203…45bc3e
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x421c1d…582b47
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x1d3e65…cea18e
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x8a8880…8d9604
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0xebf59b…f82dc4
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x484c10…9c71bc
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x3172b2…26b025
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x27c7ca…f91465
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x3ec257…28e16a
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x45ef51…9cc1b1
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x44958f…f30380
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x52050d…117a50
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0xa84820…72c8e1
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x1a2655…c9c740
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x74c37a…e104e0
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x18e266…6466b8
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0x8b03a1…e2e604
0xf629…eaf10x0495…eed9Base$0.10100%payAI226d ago0xa6b365…346163
0xf629…eaf10x0495…eed9Base$0.0001100%payAI238d ago0x4a624d…065b5d
0xf629…eaf10x0495…eed9Base$0.0001100%payAI238d ago0x28f36b…079b48

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

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

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: 0xf629…eaf1

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