Arnict
← DocumentationVerified reference

Authentication

Key lifecycle, scopes, and safe secret handling.

Bearer keys

Send the key in an Authorization header. Arnict hashes API keys at rest and never returns the secret after creation.

http
Authorization: Bearer $ARNICT_API_KEY

Key safety

Use one key per workload, keep it out of source control and browser code, and revoke it immediately if it is exposed. A verified email is required before an active key can be created.

  • The only launch scope is inference.
  • Revocation is immediate for new requests.
  • Request IDs and token counts are retained for metering; key material is not.

Reference model

qwen3.8-27b