Skip to main content

Serenity Star account

A Serenity Star account gives you direct access to Serenity Edge: you create API keys, buy prepaid credits and see your usage, all from the same place. Serenity Star also handles authentication and billing for this traffic, in the EU.

Set up​

  1. Sign in to Serenity Star, or create an account.
  2. Open the API keys section and create a key for Serenity Edge. Copy it once; it is not shown again.
  3. Add prepaid credits. Usage is deducted from the balance at the prices of your Serenity Star account.
  4. Send your first request following Getting started, with base_url set to https://api.serenityedge.ai/v1.
Preview

Self-service key creation and credit top-up for Serenity Edge inside Serenity Star are being rolled out. Until they are available to every account, write to [email protected] to get a key and an initial credit balance.

Models​

With a Serenity Star key, POST /v1/chat/completions and POST /v1/responses serve these models:

ModelAlso callable as
orion-pro-26.2orion-pro
orion-plus-26.1orion-plus
qwen3.6-35b-a3bqwen/qwen3.6-35b-a3b

The other models, qwen3.8-27b and paddleocr-vl-1.6, answer HTTP 404 with code: "model_not_found" to a Serenity Star key. The decision, embeddings, rerank and redaction endpoints answer HTTP 403 with code: "permission_denied". They need a Serenity Edge API key, from an enterprise contract.

Credits and billing​

  • Serenity Star bills your usage at the prices of your Serenity Star account. The prices in Pricing and limits are those of Serenity Edge API keys.

  • Credits are prepaid and non-transferable. Consumption is metered on the usage object of each response.

  • When the balance reaches zero, requests fail with HTTP 429 and code: "insufficient_credits" until you top up. See Errors and rate limits.

  • Invoices are issued by Serenity Star in the EU. Authentication and billing data are processed in Azure France Central; see Data residency.

Keys​

  • Create one key per application or environment so you can rotate or revoke them independently.
  • Keys carry the default rate limits of the account. Limits grow with usage; write to [email protected] if you need more sooner.
  • Revoke a key immediately if it leaks. Requests with a revoked key return HTTP 401.
Last updated on