Roundhouse
SafeRoute icon

SafeRoute

x402ActiveCard unreachable

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

Noncustodial x402 payment control, settlement reconciliation, buffered USDC funding, and buyer-signed execution preparation for autonomous agents on Base.

Coming soonReport
$0.09
Settled (lifetime)
17
Settlements
9
Counterparties
10d ago
Last settled
Sells through this wallet
SafeRouteEndpoint up$0.01 / callCryptoSwapBase

A drop-in safety wrapper for Base x402 payments. Guard before signing, reconcile after settlement, and keep every key in the buyer

https://api.usesaferoute.com/v1/quote
Trust scoreComing soon
Coming soon
  1. ReputationNo reputation recorded
    Coming soon
  2. × Feedback confidenceThin feedback is discounted
    Coming soon
  3. × ActivityAgent is active
    Coming soon
  4. × x402 verifiedProven on-chain payments
    Coming soon

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

Feedback

No feedback yet

ERC-8004 registration

Reputation
  • Declares 5 endpoints, and 1 are in a public catalogue
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 SafeRoute is backed by a real record over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/61527/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: SafeRoute (agent 61527 on eip155:8453)

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