Dashboard & API keys

The dashboard is the control plane for humans — separate from the proxy data plane.

Logging in

Dashboard login uses single sign-on (OAuth2 / OIDC). On first login your org is provisioned just-in-time, so a new user lands in a working org without manual setup. Proxy traffic itself never uses SSO — it uses API keys.

Managing API keys

From the dashboard you can:

Create a key — give it a name, and the API key is shown once; store it immediately. The name is just a label, not part of the credential.
List keys by name with their last-used time.
Disable / revoke a key — it stops working on the proxy right away.
Delete a key.

Only the SHA-256 hash of each key is stored; the plaintext key is never persisted.

Usage & billing

Credits spent against your monthly allotment, with what remains and utilisation.
The plan catalog (Basic / Pro / Enterprise) with an upgrade path.
A recent-requests log and success/error-rate charts.

See Analytics & usage for what’s measured.

API-first

The dashboard runs on the same public API you can call directly, so anything you can do in the UI — manage keys, read usage — you can automate.