Project settings
Change the project label, control monthly spending, and inspect recent administrative activity.
Settings applies to the selected project. It contains the project name, immutable ID, monthly spending limit, and recent activity log. It is not a model-configuration page: adapter rank, optimizer settings, and provider credentials are managed by the platform.
Name and identifier
Change the project name when its label needs to be clearer. Names must be nonempty and no longer than 80 characters. Renaming does not change the project ID, API keys, subject names, or historical job identifiers.
Use the copy control next to Project ID when configuring your own operational records or requesting support. The ID is useful for correlation but does not grant access by itself. Public model requests select the project from their API key rather than a project-ID body field.
Monthly spending limit
Enter a nonnegative USD amount and save. The platform converts it to integer micro-USD and enforces a hard admission limit that includes current settled spend and running reservations. The control resets by calendar month in UTC.
Set the limit to $0 to pause new paid admissions. This does not cancel already-admitted work, release its reservations, or prevent its eventual settlement. Lowering a limit below existing usage similarly blocks new work without rewriting the past.
The default for a new project is $100. This is a ceiling, not a subscription, credit grant, or promise to charge your card. You still need a prepaid balance, and automatic top-ups are not enabled.
Activity log
The recent activity table records changes such as project creation and updates, key creation and revocation, submissions, and adapter activation. It shows action, resource, and time. The current view is limited to the most recent 50 entries.
Use it to understand administrative changes, then inspect Activity for execution outcomes. The activity view is not a complete export of every read, every HTTP attempt, or every provider operation. It intentionally does not contain prompt bodies or API secrets.
Boundaries
The current console uses project ownership and scoped API keys. It does not expose team invitations, custom role definitions, single sign-on configuration, per-subject budgets, or self-service data deletion. Do not assume settings from another platform are available here.
See Spending limits for the exact budget behavior and Data handling for access or deletion requests. If a saved value appears wrong, verify the selected project before changing it again.