Admin quickstart

Create, fund, and configure a compliant Cortecs project

Use this guide if you are responsible for setting up and governing a Cortecs project. If you were invited to an existing project to connect a tool or application, follow the Member quickstart instead.

1. Create and fund the project

Register at cortecs.ai, then complete the project billing setup:

1. Add your billing address in Console > Billing.

2. Add a payment method. Credit card is recommended when funds must be available immediately.

3. Top up the project balance.

4. Configure Auto top-up if requests must continue without interruption.

See Billing for payment methods, invoices, and balance management.

Requests fail when the project balance reaches zero. Use Auto top-up or monitor the balance to avoid interruptions.

2. Invite and organize members

Open Console > Project to invite the people who will use Cortecs. Organize members into teams when departments, workloads, or internal projects need separate settings, budgets, or usage reporting.

See Teams for member assignment, the Default team, and team-specific controls.

3. Configure compliance and inference

As a project administrator, translate your organization's compliance, security, and data-processing requirements into enforced project settings before members begin sending requests.

Open Console > Inference and review:

• whether individual requests may override the saved configuration;

• Zero Data Retention and Sovereign Cloud restrictions;

• the providers that may process requests;

• quantization, model fallback, maximum tokens, and the provisioning strategy;

• whether any team needs an override of the global settings.

See Inference Settings for all controls. The Security & Compliance section explains the available data-governance options in more detail.

Disable Allow overwrite when the saved inference configuration must be enforced centrally. When it is enabled, applications may supply their own inference settings per request.

4. Set spending limits

Open Console > Budgets to define project, team, user, or API-key limits. Choose the scopes and periods that match your organization's cost controls.

See Budgets for available scopes and enforcement behavior.

5. Hand off to members

Once funding, team assignments, compliance settings, and budgets are ready, members can create their own team-scoped API keys and connect their tools. Send them the Member quickstart.