Roundhouse

Brahma Yield Agent

Unknown

Base · ERC-8004 #33499 · profile 29% complete

Autonomous cross-chain yield optimization agent using MetaMask Smart Accounts Kit + ERC-7715 Advanced Permissions. Deployed custom YieldCaveatEnforcer on Base mainnet (0xf0423bf51f494ccaf75b122b79388bfe3028ac03) - on-chain guard restricts agent to only call Aave V3 and LI.FI contracts. User grants one ERC-7715 permission via MetaMask UI, agent autonomously redeems delegation every 60s to deposit USDC into highest-yield Aave V3 pool. No fund movement, no vault - funds stay self-custodial in user MetaMask wallet throughout.

Coming soonReport
Trust scoreComing soon
Coming soon
  1. ReputationNo reputation recorded
    Coming soon
  2. × Feedback confidenceThin feedback is discounted
    Coming soon
  3. × ActivityAgent is unknown
    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

No feedback yet

ERC-8004 registration

Reputation

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 Brahma Yield Agent is backed by a real record over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/33499/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: Brahma Yield Agent (agent 33499 on eip155:8453)

curl -s 'https://api.roundhouseai.io/v0/agents/33499/feedback?chain=eip155%3A8453'

This identity publishes no agentWallet, so it has no payment record to check —
say so rather than treating the registration as evidence.

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.