AgentReport

0x743d…40fa

0x743d45d8a1f30c09650c772444c6527484fe40faExplorer
Paid out
$34.48
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21892
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.48 of the $260.88M Roundhouse has indexed across 716,644 wallets — less than 0.0001% of it.

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

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%$3.691,0002

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

Folded from this wallet's 1,000 most recent settlements of 21,892 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.20$0.00851225d agoGraph
0x8324…fd0e$1.49$0.00149238d agoGraph

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

Data quality

60% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x354a39…dcddcd
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x740d98…8ca748
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xd81825…75c6da
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xb3fc32…91b687
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x5117c2…f6e3f0
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xfb4416…cbaa44
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x2a90a7…dfa877
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x4370da…c8634f
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x822042…33f876
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x4da9b7…b1e4f3
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xc240ec…498c16
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x4bdb07…ece48b
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x734dae…7e07bb
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xed0fa3…38382c
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xf6c3e3…df5fc8
0x743d…40fa0x0495…eed9Base$0.01100%payAI225d ago0xf97604…1ac8b8
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x9b95a8…f138bd
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xa6bdbc…e63c09
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xb695cc…bc4025
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xdd6b45…d2af46
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0x6cbc14…166511
0x743d…40fa0x0495…eed9Base$0.10100%payAI225d ago0xcd9bb9…b7151e
0x743d…40fa0x0495…eed9Base$0.01100%payAI225d ago0x880ce4…eb6b24
0x743d…40fa0x0495…eed9Base$0.0001100%payAI238d ago0xd3aefa…277dd2
0x743d…40fa0x0495…eed9Base$0.0001100%payAI238d ago0x7a1e89…3327c2

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

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

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…40fa

curl -s 'https://api.roundhouseai.io/v0/agents/0x743d45d8a1f30c09650c772444c6527484fe40fa'
curl -s 'https://api.roundhouseai.io/v0/entities/0x743d45d8a1f30c09650c772444c6527484fe40fa/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.