AgentReport

0xe484…3e21

0xe4849d29df6f8754c5f425a15e7f327dfc523e21Explorer
$0.03
Paid out
$0.00
Received
2
Settlements
2
Distinct counterparties
In the 2 settlements scanned

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

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.

GroupShareSpentCallsSellers
Not in any catalogue100%$0.0322

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 2 the amount paid narrows the list to the ones listed at that price.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x8b29…721d$0.02$0.0017m agoGraph
0x7284…299c$0.01$0.0016m agoGraph

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

Data quality

67% of observed volume is with a single counterparty, in all 2 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe484…3e210x7284…299cBaseBase$0.01100%coinbase6m ago0x3ac7df…47f884
0xe484…3e210x8b29…721dBaseBase$0.02100%coinbase7m ago0x390a41…ced9bb

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

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

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: 0xe484…3e21

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