AgentReport

0xd627…2280

0xd627283d0f56f043cb46d2b5d8ad1ee471522280Explorer
Paid out
$0.88↑ 48%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
880↑ 48%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.88 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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

$0.88 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 8m ago
    $0.71
    709 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 108d ago
    $0.17
    171 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.71$0.007098m agoGraph
0x9c95…e299$0.17$0.00171108d agoGraph

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

Data quality

81% of observed volume is with a single counterparty, in all 880 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa14h ago0x574b9e…ad3201
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa15h ago0x436102…5fc6d0
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa15h ago0xe3eb1e…9d5a2d
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa16h ago0x5da19d…60fb6b
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa16h ago0xbaee23…93bd89
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa17h ago0x121f6e…53b2cf
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa18h ago0x30a20e…e2f32e
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa18h ago0x04ecec…59ad99
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa19h ago0x59b0d1…af7371
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa19h ago0x0bc0cb…019d12
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa20h ago0x8e6007…1d9834
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa20h ago0xd99a8e…1619a2
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa21h ago0xd61bb5…b54402
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa22h ago0x163d2a…64a9ac
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa22h ago0xde378f…bc0c5c
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa23h ago0x04104a…00cb7d
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa23h ago0x155ffd…5296e0
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0x00d9a9…8c2046
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0xdcd132…7dfe10
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0x0cc858…0393e0
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0xfd6113…745da7
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0x50ea27…0530f6
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0xc61551…979e91
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0x2b3cf6…fc5f50
0xd627…22800xfe80…47eeBaseBase$0.001100%fluxa1d ago0xb40876…a8e8ca

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

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

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: 0xd627…2280

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