Skip to main content

Console & billing

Use the Customer Console to manage workspaces, API keys, billing, usage, and team access.

Organizations and workspaces​

Signing up creates an organization with a Personal workspace inside it. Keys, credits, and usage belong to a workspace; you can create more workspaces and switch between them in the Console. Teammates are invited at the organization level, as Developer or Admin — Admins manage members, billing, and workspace admin actions. A workspace must be activated (funded, or covered by starter credit) before you can create API keys.

On first sign-in, the Console shows a checklist for adding billing details, buying credit, creating an API key, and testing a prompt in the Playground.

API keys​

Under API keys, you can create, reveal, rotate, and revoke credentials. See Authentication for key-management guidance.

Playground​

The Playground sends prompts to the live model from your browser. Use it to test system prompts and response formats before integrating the API.

The Use it from code panel provides the endpoint, region, model name, and examples for curl, Python, and Node.js. See the Quickstart for a complete walkthrough.

Usage​

The usage page shows activity for the last 24 hours, 7 days, or 30 days:

  • completed request counts;
  • prompt and completion token volumes, matching the fields in each response's usage object.

Rejected requests and server-side failures are not charged or included in usage totals. Monitor 429 responses in your own telemetry because they do not appear on this page. A request may still be charged if the client disconnects after processing has started. See Pricing.

Billing​

Celeris is prepaid: usage draws down a workspace credit balance.

Balances, top-ups, invoices, and usage are workspace-specific. The saved card and billing email belong to the organization, so an organization admin can use the same payment method across its workspaces without merging their spend.

General-tier usage is metered at US$2 per million prompt tokens and US$6 per million completion tokens.

Buy credits with a card (Stripe) in preset amounts of $10 / $20 / $50 / $100 or a custom amount between $10 and $1,000 per purchase. Receipts are emailed automatically, and invoice documents remain available from Billing.

When your balance reaches zero, API calls return 402 insufficient_quota until you add credit.

Commercial access​

The Console lets an organization request Commercial access. If capacity is available it activates immediately; if capacity is full, a saved card is required to join the queue. Joining does not charge the card, and inference continues to use the selected workspace's prepaid credit balance.

For a committed sustained rate, reserved capacity, custom limits, or custom terms, contact us.

Team​

Team invites collaborators to your organization by email, with roles controlling who can manage keys, billing, and members (see Organizations and workspaces). Credit is workspace-shared; keys are private to their creator unless deliberately shared with the workspace. Review and rotate keys when access changes.

Account settings​

Organization name, workspace name, and password management live under Settings.