Dashboard guide
The operator console for traffic, controls, usage, and evidence
Panicly’s dashboard is an operator console. It is organized around live traffic, spend protection, rules, request evidence, and workspace operations.
Launch-readiness summary, workspace/project status, request totals, block rate, cost saved, and fast actions.
Recent provider requests, allow/block decisions, policy reasons, and request detail forensics.
Monthly included volume, used volume, overage usage, credit-backed capacity, and plan summary.
On-demand usage packages, credit balances, Stripe checkout, and sync return flow.
Admin and operator history for keys, provider changes, project actions, and controls.
Workspace information, members, billing, project API keys, and provider keys.
Project thresholds for rate limit, abuse threshold, max tokens, and loop sensitivity.
Detected model inventory, project filter, provider filter, search, enable/disable state, and model detail routes.
Sender IP-oriented controls and sender inspection.
Country and Panicly-defined region blocking.
Emergency hold surface for immediate project traffic shutdown.
Spend, usage, and block trend surface. Current notes mark this as Pro-gated.
Most dashboard pages call a multiplexer endpoint: /api/dashboard?endpoint=.... This internal route is a large backend surface, not just a UI helper.
Plan checkout, credit checkout, checkout sync, credit sync, and portal launch.
Sentry Mode, Network Controls, Region Rules, provider keys, project API keys, project creation, and onboarding completion.
Workspace ownership is inferred from the earliest organization user row; later users are members.