Skip to main content

Console & billing

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

Organizations and workspaces​

Companies provide context for Workspaces, while keys, credits, and usage stay inside each Workspace. See Companies and workspaces for the switcher, roles, access boundaries, and settings. A workspace must be activated (by adding a payment method under Settings → Billing) before it has API keys at all; activation gives every member a private key named Default. See Keys for private versus workspace-shared keys.

On first sign-in, the Console shows a checklist for buying credit, revealing the initial API key, and sending a prompt from 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. Choose celeris-1 or Celeris-1 Magnus from the model picker; the selected model is used in the endpoint and request body.

With Thinking off, the max-output control uses each example's answer preset; the default example starts at 2,048 (the API's default when max_tokens is omitted). Turning Thinking on raises the preset for the selected example, model, and effort so reasoning leaves room for the answer. The control steps in 256-token increments. Its ceiling follows the selected model: 130,816 for celeris-1 and 16,384 for Celeris-1 Magnus. See the max_tokens guidance for how to size it.

Open Parameters to turn Thinking on when a prompt benefits from working through the problem before answering. Thinking is off by default for both models so Playground runs start on the faster path. With Celeris-1 Magnus, turning it on also reveals an Effort choice: Low, Medium, or Extra high, with Medium selected by default. Celeris-1 has one reasoning mode and does not show that input. Reasoning shares the run's max-output budget. When the response returns the working separately, the Playground shows it in a collapsible Reasoning section above the answer, collapsed by default. See Reasoning for the response shapes and budget guidance.

A run can carry up to four images alongside the prompt. Use the Attach image button, paste, or drag-and-drop (all take more than one), or pick the Read an image example, which comes with a sample receipt ready to run. Attached images are sent in the order shown, and you can remove or reorder them before running; see several images per request. The console re-encodes large images in your browser so the whole request fits the size budget, and each image counts toward the prompt's input tokens (the post-run receipt shows the exact number). See Pricing for token rates.

The Use it from code panel provides the endpoint, region, model name, and examples for curl, Python, Node.js, Go, Rust, and Java. 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;
  • uncached input, cached input, and completion token volumes. Cached input is shown separately and is not included in the uncached input figure.

Throttled (429) requests do not appear here, so track them in your own telemetry. A request may still be charged if the client disconnects after processing has started. See Security and data handling.

Billing​

Celeris is prepaid: usage draws down a workspace credit balance. Open the account menu in the bottom-left of the Console, then select Settings → Billing to manage billing. Pricing has the token rates, the purchase amounts, and how credit expiry works.

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. Receipts are emailed automatically, and invoice documents remain available under the same billing page.

Auto Top-Up​

Auto Top-Up keeps a workspace funded without a manual purchase. Under Settings → Billing, turn it on and set the balance that triggers a purchase, the amount to buy, and a monthly spending limit. Celeris charges the organization's saved card when the workspace falls below that threshold during use. Usage while the balance is already below the threshold also triggers a purchase.

Auto Top-Up on Credit Expiry is off by default. Credit expiry usually means that a service is not in use, so Celeris does not charge the saved card merely because unused credit expired. If expiry leaves the balance below the threshold, the next successful use triggers the usual automatic purchase. Turn this setting on only if you want an expiry-driven drop below the threshold to trigger the purchase immediately. This default avoids unwanted charges after a period of inactivity.

After each automatic purchase, Celeris emails the billing contact with the amount added and the new balance. The email is separate from Stripe's itemized receipt. You can change the thresholds or turn Auto Top-Up off from the same billing page.

When Auto Top-Up is off, Celeris sends one low-balance email after the balance falls to 10% of its level immediately after the latest purchase. For example, if a workspace has $0.50 left and buys $100, the next warning is sent near $10.05. Celeris sends a final email if the balance reaches zero.

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

Commercial access​

Commercial access is not self-serve in the Console. For higher limits, a committed sustained rate, reserved capacity, or custom terms, contact us. Inference continues to use the selected workspace's prepaid credit balance after activation.

Team​

Team manages collaborators; Companies and workspaces explains invitation roles and access. 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​

Company and Workspace management is described in Companies and workspaces. Password management and notification delivery choices live under Settings and follow your account across devices and organizations; turning off a channel or event suppresses future matching Console notifications or emails. Company settings always apply to the context that owns the active Workspace.