AgentReport

0x743d…f531

0x743d13b4f07994c77e3121467e55c58876dcf531Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
264
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 277d ago
    $0.03
    264 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
0x6482…b779$0.03$0.00264277d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams338d ago0x5666cf…721c73
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams338d ago0xfe940a…3b657f
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams338d ago0x969fed…5720c7
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams338d ago0x63c1fd…8f0a0b
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams338d ago0xb76122…df5ddb
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x504004…f828fc
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x79d2c4…55a183
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0xe2709d…c98a5a
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0xd183b4…7076f9
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x04811a…5c9dad
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x2ee987…49666c
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x726b8c…94dc90
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0xb2e71d…c69639
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0xd2c9c6…9337d9
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0xa35fa5…88bd45
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x485c18…9d8258
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams340d ago0x455dbd…7a49ab
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0x956354…b112d8
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0x6a05ea…7ec28a
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0xa0ec88…91a142
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0xf17da5…18feaa
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0x0741d7…0f6760
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0x8b8536…1991e9
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0x62902d…d3310a
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams341d ago0xe84127…c6d7f1

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

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

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: 0x743d…f531

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