AgentReport

0x5173…70dc

0x51736b62b336db12216cdaaff5ef0a40d8ec70dcExplorer
Paid out
$0.30
Last 7d vs prior 7d
Received
$0.70
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.30 of the $3059.84M Roundhouse has indexed across 1,397,384 wallets — less than 0.0001% of it.

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

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

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 1 the amount paid narrows the list to the ones listed at that price.

  • 0xa2b3…e4f0city-campaign-production.up.railway.appEndpoint up
    0xa2b3…e4f0 · last paid 151d ago
    $0.30
    3 calls
    ▸1 of 1 catalogued endpoints list a price this agent paid
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
0x68b3…3e77$0.00$0.701103d agoGraph
0xa2b3…e4f0$0.30$0.003151d agoGraph

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

Data quality

70% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x68b3…3e770x5173…70dcBaseBase$0.70100%fluxa103d ago0xd62263…0ae671
0x5173…70dc0xa2b3…e4f0BaseBase$0.10100%payAI151d ago0x6cfef2…db75f0
0x5173…70dc0xa2b3…e4f0BaseBase$0.10100%payAI155d ago0xb1ee36…289135
0x5173…70dc0xa2b3…e4f0BaseBase$0.10100%payAI155d ago0x5e83a1…e73679

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

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

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: 0x5173…70dc

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