Projects

Projects group configurations, keys, and requests by product, application, environment, or customer.

When to create a project

Create a project when you:

• Manage several applications or products.
• Separate development, test, and production environments.
• Group configurations by customer or department.
• Need a stable scope for configuration management.

A simple personal trial can start without one.

Create and assign

1. Open Projects and choose Create project.
2. Enter a name and verify the slug.
3. Save, then assign existing API configurations.

Use lowercase letters, numbers, and hyphens for stable slugs, such as customer-support-prod.

A configuration can belong to only one project at a time. Moving it changes how future project-scoped queries are interpreted.

Every key belonging to a configuration inherits that configuration's project scope, including replacement keys during a rotation grace period.

Assign configurations

Edit the project and select existing API configurations. One configuration can belong to only one project at a time. Before moving it, check clients and automation that depend on the current project assignment.

Recommended structures

By product:      customer-support, content-studio, internal-copilot
By environment: app-development, app-staging, app-production
By customer:    client-a, client-b, research-department

Use distinct configurations and access keys for production and test traffic; do not rely on names alone.

Boundaries

A project does not create upstreams, discover models, generate configurations, or update credentials already deployed in clients. It is an organizational scope; actual call capability still depends on upstreams, model resources, and API configurations.

Before renaming a slug or moving a configuration, check automation and external systems that may depend on the current value.

Modify a project

You can change the name, slug, and assigned configurations. Review slug dependencies and configuration ownership before saving. A project rename does not update client base URLs, model names, or stored access keys.

Example design