Authentication

API key authentication

Generation requests and /v1/models use your HiPix API key in the Authorization header:

Authorization: Bearer sk-your-api-key

Use HTTPS and store the key in a server-side environment variable. Do not substitute a dashboard login token for a generation API key.

Access failures

If a request is rejected, inspect its HTTP status and redacted error response. Check that the key exists, is enabled, has not expired, and permits the requested model and source IP. Account balance and key quota can independently prevent a paid request.

Correct the reported cause before retrying. Error codes and envelopes vary by endpoint; do not rely on a single hard-coded message.

Dashboard endpoints

The model classification and documentation endpoints under /api/pricing/ follow the pricing page’s access policy. They may be public, require dashboard login, or be disabled. The API key header above does not replace dashboard authentication for those endpoints.

Rate limiting

Requests may be subject to configured rate limits. For HTTP 429, reduce frequency and concurrency and use bounded backoff. Do not assume rate-limit headers are always present. See Rate Limits.