AgentReport

0x588a7d3f53f9a2527690ed07dda2f705b6b392cb

0x588a7d3f53f9a2527690ed07dda2f705b6b392cbExplorer

Paid out

$3.88

Last 7d vs prior 7d

Received

$0.00

Last 7d vs prior 7d

Settlements

Last 7d vs prior 7d

Distinct counterparties

Over the whole indexed history

Paid $3.88 of the $258.32M Roundhouse has indexed across 712,831 wallets — less than 0.0001% of it.

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

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.

Group	Share	Spent	Calls	Sellers
Not in any catalogue	100%	$3.88	2	1

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

0x7dbb…59e0
0x7dbb…59e0 · last paid 113d ago
$3.88
2 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

$0.00

Balance now

USDC on Base, read 0s ago

Spending power

more calls at its median payment of $1.94

—

Burn rate

nothing spent in the last 7 days

—

Runway

not spending, so nothing to run out

Inflows and outflows

Every token transfer this wallet has made, not just the x402 ones the index holds.

The transfer history behind this wallet was not read (cdp sql 400: {"correlationId":"a40099d43efb0db7-IAD","errorLink":"https://docs.cdp.coinbase.com/api-reference/v2/errors#invalid-request","errorMessage":"Limit for rows or bytes to read on leaf node exceeded, max b), so where its funds came from is unknown here. The balance above is still measured.

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

Counterparty	Paid them	Received back	Settlements	Last
0x7dbb…59e0	$3.88	$0.00	2	113d ago	Graph

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 2 observed settlements.

Organic volume $3.88 of $3.88 total.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0x588a…92cb0x7dbb…59e0	Base	$2.84	100%	0x323a…a4f2	113d ago	0x498cf0…b497d2
0x588a…92cb0x7dbb…59e0	Base	$1.04	100%	0x323a…a4f2	118d ago	0x683738…657cfb

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

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

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: 0x588a7d3f53f9a2527690ed07dda2f705b6b392cb

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