ERC-8004 identity
#59958Pa1m SEOinline registration
#59959Pa1m Redditinline registration
#59960Pa1m Hyperliquidinline registration

Website SEO auditing for AI agents. Crawls up to 500 pages and scores 20 categories across 200 rules: technical health, Core Web Vitals, structured data, crawlability, redirects, hreflang, accessibility, E-E-A-T and AI-search visibility. Returns structured JSON findings ranked by severity, plus an AI-written action plan and free-form analysis grounded in the audit. Pay-per-call in USDC on Base via x402 — no API key, no account.

AgentReport

0xe43b…4fb4

0xe43b08f2031e3332ce97c0e0ea6e8bb00bd04fb4Explorer
Paid out
$4.21
Last 7d vs prior 7d
Received
$1.52
Last 7d vs prior 7d
Settlements
15
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

Paid $4.21 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.

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

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%$4.2122

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

  • 0x0e3d…7757 · last paid 103d ago
    $4.20
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x2291…1087 · last paid 101d ago
    $0.01
    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…

ERC-8004 registration

  • Declares 5 endpoints, none of them in any catalogue we crawl

Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1

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
0x0e3d…7757$4.20$0.001103d agoGraph
0xe0ae…62a2$0.00$1.3610106d agoGraph
0xf823…f6eb$0.00$0.15242d agoGraph
0x2291…1087$0.01$0.001101d agoGraph
0x6bf5…9ded$0.00$0.005184d agoGraph

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

Data quality

73% of observed volume is with a single counterparty, in all 15 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 0xe43b…4fb4 has actually paid for over the free read API. No key, no account.

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

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: 0xe43b…4fb4

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