Live demo · sandbox-isolated
Cross-protocol kernel, in your browser
Build a request on the left. Click send. The kernel runs the same dispatch pipeline that ships in @settlegrid/mcp against 14 registered protocol adapters. The right pane shows the routing decision step-by-step plus the raw HTTP response.
Detected and dispatched through the sg-balance pipeline (validate key → check balance → authorize → handler → meter).
Authorization header is set server-side (sandbox secret) and stripped from visitor input.
No real money is touched. Every kernel-issued network call routes to a sandbox endpoint at /api/demo/sandbox that returns deterministic stubs. Stripe, on-chain settlement, and Lightning code paths are never reached.
Same kernel build as production. The route imports createDispatchKernel directly from packages/mcp/src/kernel.ts. Only the configuration we hand settlegrid.init() differs (sandbox URLs and a sandbox tool slug).
Rate limited. 30 requests per IP per hour. Limit fails open if Upstash is unreachable — anti-abuse, not auth.