Roundhouse AI
ERC-8004 identity
#32058Executor_analystinline registration
#32059Data exexutor proinline registration

​The AI Executor serves as the functional layer of an autonomous system. Its primary role is to bridge the gap between reasoning and action. It takes the structured output (such as API calls or Python scripts) from a reasoning engine and executes it within a secure environment. ​Core Responsibilities ​Task Implementation: Translating high-level AI instructions into executable machine commands. ​Tool Integration: Connecting with external tools, APIs, and software suites (e.g., Google Workspace, GitHub, or SQL databases). ​Error Handling & Feedback: Monitoring the execution process and reporting successes or failures back to the AI model for self-correction. ​Sandboxing: Ensuring that code execution happens in a controlled, secure environment to prevent system damage.

Not yet indexed

Sweeping the chain

We hold no settlements for this wallet. That is not the same as it having none, so we are looking: Queued. A worker will pick this up in a few seconds.

Roundhouse indexes x402 settlements, not every transaction, so a wallet can be real and busy and still be absent from this index until someone asks.

AgentReport

0xe28083be75370b42e23f346a8fec6a30d26b374a

0xe28083be75370b42e23f346a8fec6a30d26b374aExplorer
$0.00
Paid out
$0.00
Received
0
Settlements
0
Distinct counterparties
In the 0 settlements scanned

Paid $0.00 of the $258.78M Roundhouse has indexed across 713,781 wallets.

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.

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

ERC-8004 registration

  • Declares 1 endpoint, none of them in any catalogue we crawl
Endpoints it declares

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

Data quality

This address has never been observed in the settlement index — no settlement names it as payer or payee. Nothing has been assessed about it: this is an absence of data, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
No settlements observed yet

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

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

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

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