Console and workspaces
Manage team API tasks, usage and budgets while keeping personal payments separate.
The Console is the signed-in management interface. Customer applications use the Bearer API at /api/v1/* or the /v1 compatibility endpoints. Authenticated Console requests use session cookies and CSRF protection; public catalog and budget views are exceptions for the website. Do not copy browser cookies into your backend.
Stable entry points
Console · API Keys · Logs · Usage · Billing · Team
Choose an account or workspace scope on Logs, Usage and Billing. Selection carries between these views; changing scope reloads the data. Shared views include tasks created through that workspace’s API keys, including historical tasks.
Roles and visibility
Every member can read task summaries and usage. owner, admin and developer can also read task inputs and outputs and request output download links. owner, admin and billing can read task-related workspace ledger entries; the owner’s wallet balance, top-up history, payment details and personal statements are excluded.
owner and admin manage members; owner, admin and developer manage workspace keys; owner, admin and billing change workspace budgets. readonly changes none of these. An admin cannot grant or change the admin role or promote another member to owner.
Budgets and account billing
Daily and monthly workspace limits combine with API-key spend, model and IP limits. A rejection creates neither a task nor a new hold. The workspace owner is the billing account for new tasks; transferring ownership moves keys to the new owner. Historical tasks retain their original billing account. A budget of 0 means no limit at that layer.
Task actions remain restricted to the task’s billing account. Shared read access does not grant retry, history removal, wallet adjustment or refunds. Removing settled task content is not cancellation and preserves billing facts.