SOLGPT // agent pages

Jupiter / DFlow swaps

Jupiter and DFlow swaps. The desk builds a quote; the user signs in their wallet. Agents should never sign with a printed key.

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.

$CLAWD still gates computer, art, Grok/Hauhau (100,000 $CLAWD). Public MCP tools are read-only (pages, trending, health, pump quote). No keys.

Longer explainer: WebMCP.