Set up StateSet Console
The console is the operator UI: integrations, agent monitoring, and operations dashboards in one
place. It sits on three backing services — Hasura for data, the Sandbox API for agent execution, and
billing — and most setup problems are one of those three not being reachable.
Prerequisites
- A StateSet workspace and API key
- A Hasura endpoint and its admin secret
- Sandbox API access
Set the environment:
The Hasura admin secret grants unrestricted data access. Keep it server-side in the console’s
environment — never expose it to the browser, and use a least-privilege role for anything
client-facing.
Verify each connection
Check the three dependencies in order, because a blank dashboard tells you nothing about which one
failed:
- Hasura — the overview dashboard renders data. If it’s empty, query the endpoint directly with
the same secret.
- Sandbox — the agent console lists sandboxes. A spinner here is
SANDBOX_API_URL unreachable.
- Billing — usage figures appear on the billing page.
Stand up a staging console against staging services before pointing one at production. The console
can act on live data — the agent pipeline
includes execution, not just observation. 