Developer dashboard
Where to manage API keys, end users, usage, and billing.
Developer dashboard
Everything for programmatic access lives under Developer in the Cosmo web app. It is restricted to workspace admins.
| Section | What it is for |
|---|---|
| Overview | Getting-started snippets and current key state |
| API Keys | Create, inspect, and revoke keys |
| External Users | The end users you have minted tokens for |
| Usage | Session and metering counters for the period |
| Billing | Plan and payment method for programmatic use |
API Keys
The list shows each key's name, prefix (the leading characters, so you can identify a key without exposing it), scopes, creation time, and status.
New API key takes a name and a scope selection. The full value appears once, at creation — copy it then. Cosmo stores only a hash and cannot show it again.
Revoking is immediate and irreversible: subsequent requests with that key fail authentication. Create and roll out a replacement before revoking one that is in service. See API keys for the rotation sequence.
External Users
Each end user you mint a token for is provisioned as an external user, keyed by
the external_user_id you supply. Minting is idempotent per
(workspace, external_user_id), so the same identifier always maps to the same
external user rather than creating duplicates.
This is the surface for seeing who your integration has created.
Usage
Counters for the current period. See What is metered? for what each one counts and how it is measured.
Billing
Plan and payment method governing programmatic access. Realtime sessions require an active plan; a session-start rejected for billing reasons surfaces as an authorization failure rather than a session error.