This page shows where the site lives, where the operator explorer lives, which AI systems are named in the stack, and which endpoints expose invoices, receipts, anchoring, and UnyKorn rail health.
Primary public narrative and system launch surface.
Static operator map with optional live facilitator probes.
Canonical chain-level transaction and address explorer.
Enter gateway and facilitator base URLs to probe the full operating loop: gateway health, paid-route challenge behavior, invoices, receipts, anchoring, and UnyKorn rail health. If you are on the public HTTPS site, a plain http://127.0.0.1 address points to your own machine and will usually be blocked by the browser.
The current stack has explicit named systems for market, compliance, orchestration, content, invoice export, and federated agent traffic. A dedicated Moltbot package was not present in the repo, so the orchestration lane is surfaced here as MoltMesh.
The stack now includes a named load runner that rotates traffic across the agent systems and route families. It measures challenge-path throughput and snapshots explorer surfaces after the run.