ERC-8004 identity
#23009Agent #23009QmaPFkjo6VmQfxEViWAzZ164Xpe6LrywfzexFaFCyViRvF
AgentReport

0xe959…a951

0xe959e67ac2786631f40f5e1dcb6f149a33cea951Explorer
$510.00
Paid out
$0.00
Received
102
Settlements
1
Distinct counterparties
Over the whole indexed history

Paid $510.00 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (102)

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%$510.001021

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

  • 0x379a…1397 · last paid 380d ago
    $510.00
    102 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…

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x379a…1397$510.00$0.00102380d agoGraph

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

Organic volume $510.00 of $510.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x8f1297…913218
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0xbe2d19…463f1a
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x1b75fa…beeda4
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x836c12…20ee23
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x2dc54d…e1a708
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x76d564…d54e39
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x366ee3…d1ce24
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x995d4c…beae12
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x629b73…da385e
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0xd3e180…138e06
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0x552025…5d5a2f
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0xa9e939…6e0ff8
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0x63b896…a57795
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0x799e11…77cfc9
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0x6dc351…f081ab
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0xb19bda…a990aa
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0xa2606f…fe1d40
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0xe92924…36d24b
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0xa803b8…e6b854
0xe959…a9510x379a…1397EthereumEthereum$5.0050%0xea77…834c380d ago0x2081da…d5f404
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x0a6efc…dd9f82
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x227036…9ae154
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x2a574c…5829cd
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x88a914…e47107
0xe959…a9510x379a…1397EthereumEthereum$5.0070%0xea77…834c380d ago0x3e5ad7…a5941e

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

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

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: 0xe959…a951

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