Developer dashboard
Where to manage API keys, end users, usage, and billing.
Everything for programmatic access lives under Developer at platform.askcosmo.ai. It's restricted to workspace admins.
| Section | What it's 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 |
Manage 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.
Create 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 can't 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's in service. See API keys for the rotation sequence.
Manage 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.
Review usage
Counters for the current period. See What's metered for what each one counts and how it's measured.
Manage billing
Plan and payment method governing programmatic access. An organization gets a
one-time free voice grant; once it is spent, sessions need a paid plan. Billing
rejections fail the session-start call with a 402 — see
Limits.