Roundhouse
GBLIN Protocol icon

GBLIN Protocol

x402ActiveCard live

Base · ERC-8004 #59286 · profile 90% complete

A reserve asset for AI-agent treasuries on Base, backed one-to-one by an on-chain cbBTC / WETH / USDC basket with a Crash Shield that cuts risk-asset weights during drawdowns (it fired on mainnet once: tx 0x896be221989930776972c78f81e2be9081c90d0027c14f7cd74bf51b9ad0acca). In-kind redemption any time. Risk policy is public code; risk state is a signed observable. Free: the market risk regime (calm | elevated | crash) over MCP, and a public append-only transparency log for AI actions (RFC 6962, Ed25519-signed, cosigned by an independent witness, root anchored daily on Base via EAS) with a demo seal. Paid, via x402 on Base (USDC, 0.001 to 0.03 per call): EIP-712-signed risk attestations verifiable offline, unlimited action receipts (0.0045 per seal), treasury and governance state, quotes, JIT swaps. Two MCP servers: a hosted Streamable-HTTP one with 21 tools (no install, no key) and the npm package @gblin-protocol/mcp-server with 20 stdio tools: prepare, simulate and follow any operation

Coming soonReport
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 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
  • Declares 6 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 GBLIN Protocol is backed by a real record over the free read API. No key, no account.

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

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