Your console is the workspace itself
There is no separate developer console to learn. API keys, usage, billing and every setting live in the signed-in workspace, next to the Bots they belong to.
You will be asked to sign in first, and then taken straight to the screen you chose.
Your own screens
Home
Give a task, see what your Bots are doing and pick up where you left off.
/homeSettings › API keys
Create and revoke named keys with their scopes and expiry, register apps, set up embedded chats and copy MCP addresses.
/settings/api-keysSettings › Usage
What your own work has used this month, the budgets you own and the time your Bots saved.
/settings/usageSettings › Billing
Your plan, your credits and credit packs, where billing is switched on for the workspace.
/settings/billingApprovals
Every action waiting for your decision, with what the Bot wants to do and what it saw.
/approvalsSettings
Your language, notifications, connected accounts and saved passwords.
/settingsThe admin console
People with an administrator role also see Admin: people and groups, model credentials, boundary rules, budgets and usage, the audit trail, API key quotas and allowed MCP clients. Others are not shown it.
Building something?
Make a key in the workspace, then follow the API quickstart.