AgentReport

multipassport.eth

0x0230c6dd5db1d3f871386a3ce1a5a836b2590044Explorer
Multipassport.eth
Paid out
$200.81
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
16
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $200.81 of the $3061.41M Roundhouse has indexed across 1,398,667 wallets — less than 0.0001% of it.

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

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

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

  • 0x5c7b…35c5 · last paid 9m ago
    $200.81
    16 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
0x5c7b…35c5$200.81$0.00169m 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 16 observed settlements.

Organic volume $200.81 of $200.81 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a9m ago0x93ca7f…7e7ec7
multipassport.eth0x5c7b…35c5EthereumEthereum$11.8170%0xd016…b67a4d ago0xa19bc2…af14eb
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d19d ago0xad102f…49b2ff
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d32d ago0x223d05…5ba018
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d153d ago0x2227a7…7da847
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a153d ago0x64266d…2d2192
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xe0df…59a1157d ago0x4931fa…aefbba
multipassport.eth0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a171d ago0x2a9763…89f486
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a179d ago0x05fd3d…407430
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a180d ago0x2348c5…7e295b
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a188d ago0x918cfb…9ea096
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de194d ago0x94ac07…8b4284
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a200d ago0xac419e…fb8c75
multipassport.eth0x5c7b…35c5EthereumEthereum$21.0070%0xc10a…ae5d201d ago0x86b251…5f1c62
multipassport.eth0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a217d ago0xf22f41…95aadf
multipassport.eth0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a217d ago0xe407da…988ba7

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

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

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: multipassport.eth

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