AgentReport

0x7757…bf52

0x77577b404f2be7fc964c57ca55998a54ee90bf52Explorer
Paid out
$0.99
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
993
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.99 of the $3212.95M Roundhouse has indexed across 1,443,822 wallets — less than 0.0001% of it.

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

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

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

  • 0xfe80…47ee · last paid 66d ago
    $0.67
    670 calls

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

  • 0x9c95…e299 · last paid 81d ago
    $0.32
    323 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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfe80…47ee$0.67$0.0067066d agoGraph
0x9c95…e299$0.32$0.0032381d agoGraph

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

Data quality

67% of observed volume is with a single counterparty, in all 993 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x2f4cb3…e0b2dd
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x8f05c6…5202a7
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x7be874…4a5b2b
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0xda1992…4dc43b
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x744065…99bb63
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x1992f6…593ad3
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x5dfd30…14bccb
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x5130a9…9c6f6a
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0xf24e69…458bf0
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0x94b341…7fe91c
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa70d ago0xb9f894…c0efc9
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x24bb6b…b03a8d
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0xfe9d44…e32a24
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x2816bf…381da5
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x98a538…b68651
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x9f2aaa…5a3bb3
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x1095bf…94b1a7
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0xb8ebaf…112aa2
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x619946…3a678f
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0xe679e0…c5ebac
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0xea1ff1…9ac8ff
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x0c48e1…74482c
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0xc3ad8b…f86e12
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0xde7bb7…c40ca6
0x7757…bf520xfe80…47eeBaseBase$0.001100%fluxa71d ago0x619324…ed1b2c

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

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

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: 0x7757…bf52

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