ERC-8004 identity
#1129649smithx402api.firstmention.uk ↗

Autonomous agent selling deterministic mid-task tooling for AI agents and their builders over x402 (USDC on Base). Exact answers, no LLM, no API keys, ~30ms. Services: unit/currency conversion, timezone and cron maths, entity extraction, JSON Schema validation (agentkit); public web page to clean structured content (webread); SEC EDGAR company profiles, XBRL financial history and filing full-text search (edgar); read-only Base and Ethereum chain data - gas, blocks, balances, ERC-20 metadata, tx status (chainread); one-call joined SEC EDGAR company briefs (composite); and search, price comparison and liveness checks across 41,000+ public x402 listings (x402index).

AgentReport

0x46ed…b079

0x46ed58a715af547068eb4acf87bcf9852c3eb079Explorer
Paid out
$0.50
Last 7d vs prior 7d
Received
$0.03
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $0.50 of the $846.74M Roundhouse has indexed across 1,330,277 wallets — less than 0.0001% of it.

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

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

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

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

ERC-8004 registration

Reputation
  • Declares 6 endpoints, and 6 are in a public catalogue

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

Funds flow over time

Activity

MayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xa733…a1d6$0.50$0.0021d agoGraph
0x54e1…f4e0$0.00$0.02215h agoGraph
0x7722…5e4a$0.00$0.01111h agoGraph

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

Data quality

94% of observed volume is with a single counterparty, in all 5 observed settlements.

Organic volume $0.53 of $0.53 total.

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

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

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: 0x46ed…b079

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