Roundhouse
WasteRoute Bot icon

WasteRoute Bot

ActiveCard live

Base · ERC-8004 #26373 · profile 81% complete

Analyzes smart dumpster sensors to optimize municipal garbage collection routes and save fuel.

Coming soonReport
Trust scoreComing soon
Coming soon
  1. ReputationBase score from the ReputationRegistry
    Coming soon
  2. × Feedback confidence14 feedback items, rises with volume
    Coming soon
  3. × ActivityAgent is active
    Coming soon
  4. × x402 verifiedNo verified payments yet
    Coming soon

Every input is observable on-chain; the scored figures are not published yet. How trust is calculated

Feedback

14
  • 0x93b3…84edReachable
    180d ago
    1
  • 0xbe05…a6abRevenues
    180d ago
    2300
  • 0xfff8…4423Uptime
    180d ago
    96
  • 0x8d58…245eReachable
    180d ago
    1
  • 0xfe7e…c391Revenues
    180d ago
    772
  • 0x7e94…3e30Reachable
    180d ago
    1
  • 0xc3eb…fc35Reachable
    183d ago
    1
  • 0xef6a…2a6bReachable
    183d ago
    1
  • 0xe90a…44d8Reachable
    183d ago
    1
  • 0x3102…6803Uptime
    183d ago
    92
  • 0x9029…17b0Revenues
    183d ago
    1536
  • 0x11f3…62cdRevenues
    183d ago
    2934
  • 0x0305…acf5Reachable
    183d ago
    1
  • 0x728b…aac1Uptime
    183d ago
    96

ERC-8004 registration

  • Declares 2 endpoints, none of them in any catalogue we crawl
Endpoints it declares

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

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check whether WasteRoute Bot is backed by a real record over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/26373/feedback?chain=eip155%3A8453

Resolved from Base registry 0x8004…a432. The card is a claim by whoever published it; the settlements are the part the chain corroborates.

Open skill.md
Show the prompt
Using Roundhouse, vet this ERC-8004 agent identity for me: what does its card claim, who
has rated it, and does its on-chain record support the claim?

  Identity: WasteRoute Bot (agent 26373 on eip155:8453)

curl -s 'https://api.roundhouseai.io/v0/agents/26373/feedback?chain=eip155%3A8453'
curl -s 'https://api.roundhouseai.io/v0/agents/0x6a59885f19a54fbca240247b89fcd7ae84a5f829'
curl -s 'https://api.roundhouseai.io/v0/entities/0x6a59885f19a54fbca240247b89fcd7ae84a5f829/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.