Terms

Short terms for accounts, API keys, and billing.

These terms cover the basics of using coFlex: account responsibility, issued keys, billing, and the cases where access may be limited or changed.

Terms summary

The short version of access, billing, and account responsibility.

AccountsEach account is responsible for its own keys and usage.
BillingPlans and API balance are handled separately.

Access

coFlex provides managed GPT-5 access through public pages and authenticated workspaces, including IDE, CLI, and API usage.

Accounts and keys

Each account is responsible for activity that happens through its issued keys and workspace access. Keys may be rotated, revoked, or limited if they are exposed or misused.

Acceptable use

The service may not be used for abuse, unlawful activity, deliberate overload, credential misuse, or attempts to bypass limits and access controls.

Availability

Model access, routing behavior, limits, and workspace features may change over time as providers and infrastructure change.

Billing

Where billing is enabled, plans cover regular coding workflows and API balance is handled separately for direct API usage. Accounts may be restricted for abuse, policy violations, or unpaid balances.

Third-party services

coFlex depends on external providers for models, authentication, and infrastructure, so issues with those providers can affect the service.