Credits, Keys, And Billing

Prepay usage, manage one-time-visible API keys, and understand how Aegis charges requests.

Prepaid Credits

Aegis uses prepaid credits instead of separate upstream provider accounts. Add balance from the Billing screen before you send production traffic.

Every request draws from that balance, so you can run agents without monthly invoice surprises spread across multiple vendors.

API Key Lifecycle

Create keys from Console > API Keys. Keys are labeled, shown once at creation time, and can be deleted later from the same page.

  • Use separate keys for local development, CI, and production agents.
  • Rotate a key immediately if it lands in shell history, logs, or a shared paste.
  • Deleting a key stops every client that still uses it.

Model Billing Behavior

Aegis keys are not model-locked. The client chooses the model on each request, and billing follows the actual routed usage.

Use the Models page to compare context limits and pricing characteristics before pinning one model in an agent config.