AgentReport

0x7627…f528

0x7627fe9fac00cbb86f42d04235fb738f3809f528Explorer
Paid out
$0.95
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
945
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.95 of the $3060.46M Roundhouse has indexed across 1,398,118 wallets — less than 0.0001% of it.

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

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.959452

$0.95 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 67d ago
    $0.60
    600 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 77d ago
    $0.35
    345 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.60$0.0060067d agoGraph
0x9c95…e299$0.35$0.0034577d agoGraph

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

Data quality

63% of observed volume is with a single counterparty, in all 945 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0x81ea7b…71e92e
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0xdb6ff1…7343b3
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0x5021d0…ed3d7c
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0xc5040d…a85432
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0xc43a23…6282d3
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0x0b2a46…9bce7b
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0x822e7b…ba8828
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0x9dd869…ea7d5a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0xa34abe…da9e7f
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa70d ago0x4b43ba…993ae1
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xadd050…92a14a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0x1a4146…b7601d
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xc87008…34716b
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xd0afc8…3a7c2a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xb14154…5923fe
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0x00052e…ac88af
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xc74b24…f73445
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xc69cb3…69c4dd
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0x3fc663…748735
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0x3d63a5…dfdcf0
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xf71af6…60be8a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xe77f6b…935f12
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa71d ago0xba4320…30aa51
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa72d ago0x616e90…edbeff
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa72d ago0x6a9fe0…a2d349

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

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

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: 0x7627…f528

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