ERC-8004 identity
#55057Agent #55057QmZNqo92Ui52XTZsUcGmJp6wKVrTYEG2qkvYbCheUUNpYy
AgentReport

0x641a…feeb

0x641a34253eb11fe456c6137de0a1a579a5d9feebExplorer
$0.02
Paid out
$0.00
Received
4
Settlements
3
Distinct counterparties
In the 4 settlements scanned

Paid $0.02 of the $845.42M Roundhouse has indexed across 1,327,784 wallets — less than 0.0001% of it.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

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

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
Location & Weather63%$0.0121
Not in any catalogue38%$0.00622

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

  • X Paywww.api-xpay.comIP intelligence?Endpoint up
    0x589a…b3d8 · last paid 10d ago
    $0.01
    2 calls
    ▸9 of 14 catalogued endpoints list a price this agent paid

    6 further catalogued endpoints not listed.

  • 0x2932…4f60defi.hugen.tokyoEndpoint up
    0x2932…4f60 · last paid 10d ago
    $0.005
    1 call
    ▸4 of 83 catalogued endpoints list a price this agent paid

    75 further catalogued endpoints not listed.

  • 0x6026…efb7 · last paid 10d ago
    $0.001
    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…

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x589a…b3d8$0.01$0.00210d agoGraph
0x2932…4f60$0.005$0.00110d agoGraph
0x6026…efb7$0.001$0.00110d agoGraph

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

Data quality

63% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

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

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

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: 0x641a…feeb

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