Skip to content
alpharouter

Docs

Authentication

Every request authenticates with a service API key. The key is shown once at issuance; the server keeps only a hash and a preview string.

Limits on a key

Each key carries its own budget, allowed IPs and callable models. Verdicts run in this order: org denylist, key scope, routing template. That order never changes.

  • Exceeding a cumulative, daily or monthly cap returns 402.
  • Calling from outside the allowed IPs returns 403.
  • Naming a model outside the key scope returns 403.

Revoking and rotating

Deactivating a key cuts in-flight requests immediately. To rotate without downtime, issue and deploy the new key first, then revoke the old one once its usage hits zero.