CLAWD Gateway

SOLGPT // agent pages

Orgo computer

Public desk. Anyone can open /computer. Deploying Orgo, E2B, Browser Use, Smol Machines, or Firecrawl Interact spends the desk keys and needs a signed-in wallet that holds 100,000 $CLAWD, the exclusive admin wallet, or $4.20/month via MoonPay Commerce / Helio / x402. Unsigned calls to those APIs return 401. Keys stay on the server.

Back to agent sitemap ยท SPA: /computer

Orgo / E2B / Smol / Browser Use give an agent a real computer (desktop + browser) to operate the desk. Use that computer to open /llms.txt and /agent/ โ€” not the React SPA โ€” unless a human is driving.

Never print VNC passwords, API keys, or wallet secrets that appear on the desktop. SPA: /computer.

What this does and how it works

Two parts sit in front of the origin. Same for these static pages and the React SPA.

  1. Edge/origin injects one line: a module script at /.webmcp/bridge.js with data-packs="c2pa,mcp-server-client" and data-mcp-url="/mcp". Cloudflare may also inject this at the edge. This origin copy is the fallback.
  2. The bridge finds document.modelContext. If the browser has no WebMCP surface, it no-ops and the page is unchanged.

Packs register MCP tools. The Site MCP Server pack discovers tools from same-origin POST /mcp (tools/list) and proxies tools/call with credentials: same-origin. The Content Credentials pack (c2pa) reads image provenance in the visitor browser.

Agents already speaking MCP can drive the page. clawd-bot computers: open /llms.txt then /agent/ then call /mcp.

Computer spend still needs 100,000 $CLAWD or $4.20/month. Public MCP tools are read-only (pages, trending, health, pump quote). No keys.

Longer explainer: WebMCP.