Console screens

Every screen in the console, what it shows, and the columns on its tables, as shipped.

The console is at console.router.superprotocol.com. This page covers the screens an account holder uses. A deployment’s operator sees one further group in the sidebar, which this documentation does not cover.

Workspace

Overview

Spend, requests, tokens and evidence coverage for the current period, as four tiles, and the deployment's endpoints as a table: Endpoint, TEE, Evidence digest, Evidence, Tokens (30d).

Evidence is one of Published, Stale or Not published: whether the platform had a fresh bundle for the endpoint. It is a fact about publication, never a verdict. The digest shown here is the one you compare with what gatekeeper endpoint trust add --from-upstream prints.

Evidence coverage is the share of generations served while a fresh bundle was published for the endpoint that served them. Not a verification rate.

Models

Every model the router serves: Model, Endpoint, TEE, Context, Input /1M, Output /1M, Attestation. A filter by TEE sits above the table, starting at All TEEs. Prices are dollars per million tokens. Models served by external endpoints appear as ordinary rows; the attestation column says whether a model is available.

Chat

Talk to a served model, with the endpoint verified in this browser first. See Chat.

Access

API Keys

Issue, scope and revoke keys, and connect a client. Columns: Key, Model scope, Expires, Last used, Usage, Limit. A revoked key stays in the list with a Revoked badge. The How to connect card under the table carries the Gatekeeper setup block and the client snippets; API keys walks through the dialogs.

Insight

Activity

Spend and usage over time, by model and by key: Total spend, Requests, Token volume, Time to first token, Evidence coverage, then a Token volume over time chart, usage by model, and the top keys. A range picker chooses the window.

Logs

Per-generation metering: Time, Model, API key, Input, Output, Cost, Speed, TTFT, Status. Filters by model, key and status. Prompt content is never stored, so there is nothing here but the metering. The request id a client receives in X-Confidential-Router-Generation-Id is the row's id.

Account

Credits

Balance, transactions, top-ups and auto top-up. Transactions: Date, Kind, Description, Amount, Receipt. What each kind means is on Credits.

Profile

Your account, what this workspace spent, how much of it came with published evidence, and your top models.

Preferences

Account (signed in as, workspace), Email receipts, Desktop notifications, and Evidence: Archive quotes, Retention window, Notify on measurement change, and Export evidence bundle, which downloads the signed bundles the router stored for a date range so they can be verified offline.

Sign in offers what the deployment is configured for. On production that is a one-time code mailed to your address (Email me a code); there are no passwords. A further button on that screen is the operator’s own way in and is not for an account holder. Create an account is the same code flow with a name and the invitation; see Install and send a verified request.