AgentReport

0xfaa9…8011

0xfaa9ec7cb1e80dd596af79254eb017bb2a9c8011Explorer
Paid out
$178.65
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
443
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $178.65 of the $262.06M Roundhouse has indexed across 718,832 wallets — less than 0.0001% of it.

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

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%$178.654431

$178.65 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.

  • 0xef43…6c7f · last paid 243d ago
    $178.65
    443 calls

    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

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xef43…6c7f$178.65$0.00443243d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 443 observed settlements.

Organic volume $178.65 of $178.65 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xf285fe…982943
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x44239c…8897e0
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x8673f0…283b2f
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x3e635d…9cc14b
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xa7550e…cf1c9d
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x0c5ac0…2f4eba
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xbb04ef…01cf4c
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xb05bac…a8e62c
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xa6481c…ab8d96
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x0f3d0a…3d86e9
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xee25c6…107cc2
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x1c0658…704c52
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x72638f…8da1ac
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xcd43a1…5f8c24
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x3fc567…bcc809
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x40c9d1…f67f4c
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x81c6c3…15ddd1
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x639b81…210853
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x5dc228…45caeb
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xef1457…eb5525
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x82e8bf…21f283
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x5f7a7c…f328e1
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0xe2e8f6…f7bf06
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x016a62…6d12d4
0xfaa9…80110xef43…6c7fBase$0.50100%virtuals243d ago0x3c17b9…845944

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

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

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: 0xfaa9…8011

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