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 $3061.41M Roundhouse has indexed across 1,398,256 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%fluxa73d ago0x57f687…f39d6a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa73d ago0x874704…d0dbb5
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa73d ago0xd267d2…f667e4
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa73d ago0xa7dbbd…4231b1
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa73d ago0x925da6…68b691
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa73d ago0xc20716…eee512
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa73d ago0xac344d…c9c7bb
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x1b5689…4aad3a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xe71e5e…632f9a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x2bcfa7…60a1d7
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x7cd301…9a2a82
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xaa1612…bebfff
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x62fe46…a8b203
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x4bf7b8…7b2b30
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xcc3753…1bd374
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xa26284…12b62e
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xfbe809…5bc62b
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xce2aa6…167c17
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xb723d8…304724
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xb0161d…318333
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xd73e0d…d905d2
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x3b8b6e…038918
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0xf347f9…5d6e03
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x1b20ce…7974e8
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa74d ago0x2cb38c…a7aef5

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.