API Authentication
Every AI endpoint requires an active API key. Send the key in the X-API-Key request header over HTTPS. Keys are managed from the developer portal and are only shown in full immediately after creation.
Provisioning Key Tokens
Sign in through the developer portal.
Open API Keys and create a key for your application.
Choose a name, permissions, and optional per-key limits.
Copy the generated key before closing. It cannot be retrieved later; create a replacement if it is lost.
Header Reference Schema
Populate downstream operational request executions using standard key headers:
curl -X POST https://aiservice.prabisha.com/chat \
-H "X-API-Key: your-api-key-here" \
-H "Content-Type: application/json" \
-d '{
"messages": [{"role": "user", "content": "Hello!"}]
}'
Security: Do not expose secret API keys in browser code or commit them to source control. Call the gateway from a trusted server and store the key in a secret manager or environment variable.
API Key Scopes Matrix
| Scope Type | Downstream Queue Access Route Target |
|---|---|
| CHAT | Scope metadata is configurable in the portal. Endpoint authorization currently validates the key status; it does not enforce individual scope values. |
| IMAGE | Do not use scope metadata as a security boundary until endpoint-level scope enforcement is enabled. |
| VIDEO | Video generation is not currently enabled. |
| EMBEDDINGS | Embedding requests require a valid active API key. |