Projects and API keys
Understand the resource boundary for credentials, model access, usage, and billing.
Projects
A project is the workspace that owns your application configuration. Start with the default Default Project workspace, or create separate projects for different applications, teams, or environments.
Projects are the boundary for your configuration and account data. Each project binds and isolates:
- API keys and their scopes
- model profiles and routing configuration
- usage and credit balances
- billing activity and charges
When you create a new project in the future, it will have its own API keys, model profiles, usage, and billing context.
API keys
An API key authenticates requests for the project it belongs to. Create separate keys for each deployed service, give the smallest suitable scope, and revoke a key immediately if it is exposed.
Star OS shows a key secret only when it is created. Store it in your server-side secret manager before leaving the creation dialog.
Model selection and routing
Model profiles are configured per project. Use the Console to inspect the models available to your project and configure the profiles that your application can use. Smart Routing is designed to select an appropriate provider and model according to the project's configuration; your application should not embed provider credentials.