Skip to Content
FAQ

FAQ

Request errors

CodeMeaningCheck first
401UnauthorizedKey missing, wrong, disabled or deleted. The header must be Authorization: Bearer sk-...
402Insufficient balancePersonal balance for a personal key; enterprise balance for a shared key
403RejectedUsually the member quota is exhausted, or the requested model group is not allowed. A suspended enterprise also rejects
429Rate limitedThe gateway applies a global limit per IP and time window. Reduce concurrency or retry later
404 / model not foundModel not availableCheck models and pricing 

Model names are whatever the platform currently serves. Every example in these docs uses a placeholder, because availability and grouping change. On “model not found”, check the pricing page before suspecting your key.

If you get 401 and are sure the key is right, check whether you used an enterprise shared key where a personal one was expected, or vice versa — both work, but they are billed differently. See Keys and authentication.

Sign-in and console

  • Cannot sign in — use alltokens.si/sign-in . The site sets secure cookies and requires HTTPS: opening it over http:// will not hold a session.
  • A section is missing — it is administrator-only. See the permission matrix in the console overview.
  • “You are not a member of an enterprise yet” — join through an invitation link first: Accepting an invitation.
  • “This enterprise is not active” — it was suspended or closed; contact the owner or the platform.
  • You belong to several enterprises — use the switcher at the top of the console.

Invitations

  • The link fails or is invalid — expired, revoked, uses exhausted, or you were targeted at a different email. See Accepting an invitation.
  • Lost the token — plaintext is shown once and only a hash is stored, so it cannot be recovered. Ask an administrator to revoke and reissue.
  • A member cannot join — check the enterprise member cap.

Quotas and billing

  • Out of quota — administrators adjust member limits in Members; the enterprise balance is handled by the platform (Balance and ledger).
  • I was refunded but the request count did not drop — by design. Counts record that a settlement happened; refunds do not un-count. See Usage.
  • No top-up option visible — availability follows what the billing page actually offers.

Invoicing, contracts and support

None of this has a published position, and these docs commit to nothing. Refunds, invoicing, balance validity, contract settlement, a unified SLA, incident notices, and the legal entity, support channels and response times are all unpublished.

Before paying, procuring, or relying on this for compliance, read the main site’s Service and data processing page . It summarises what is published and what is still pending, and takes precedence over these docs.

To be completed: official support channels and response times, the invoicing process, refund and contract settlement rules, SLA and incident notice entry points. These need an official position from the business — we will not fill them with guesses.

Still stuck

Identify the category above, then send the platform: the request time (Asia/Shanghai), the error code, which kind of key you used, and the model name. That is usually enough to locate it.