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 $3068.58M Roundhouse has indexed across 1,402,722 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%daydreams323d ago0xa77066…f42146
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams323d ago0x796cbb…3867b5
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams323d ago0x6dcc61…ddc04a
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0x311ca2…2a93e1
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0xaa3c2a…b1fc86
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0x2fac92…1a2090
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0xc39463…9d18c9
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0x904584…7a1e5e
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0xda6b54…aff530
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0x29346c…de7873
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams324d ago0x28c130…ce8ce2
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x23d0a5…b103b6
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x4f7845…ad695b
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x99229f…fbdbe5
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0xd166b9…27e62b
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0xfdeb27…677fe1
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x4c611f…2914de
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x463f77…85fffb
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x2ae9c6…a6723c
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x999209…76a202
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0xf7201a…38e2d8
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0xedd99e…ff291a
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams325d ago0x214ed8…210bfc
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams326d ago0x3b833d…1d92cb
0x743d…f5310x6482…b779BaseBase$0.0001100%daydreams326d ago0xf8d4bd…81c7a4

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.