AgentReport

0xda1d63b7200299d37374bf847b83cdd4b7fdb8f9

0xda1d63b7200299d37374bf847b83cdd4b7fdb8f9Explorer
Paid out
$0.04
Last 7d vs prior 7d
Received
$0.04
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.04 of the $260.82M Roundhouse has indexed across 716,570 wallets — less than 0.0001% of it.

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

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

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

  • 0x1343…4abb · last paid 119d ago
    $0.04
    1 call

    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

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x1343…4abb$0.04$0.001119d agoGraph
0xb90a…9ae4$0.00$0.041121d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 2 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xda1d…b8f90x1343…4abbBase$0.04100%fluxa119d ago0xf9c142…50c229
0xb90a…9ae40xda1d…b8f9Base$0.04100%fluxa121d ago0xe13caf…5bb101

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

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

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: 0xda1d63b7200299d37374bf847b83cdd4b7fdb8f9

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