Home
/
Getting Started
Getting Started
Prerequisites: You’ll need your Gateway X-Key and the base URL.
1
Save Base URL & X-Key
-
Default Base URL:
https://api.alephbasys.ir
-
Open Settings and paste your
X-Key
2
Make Your First Request
Test the health endpoint.
curl -X GET "https://api.alephbasys.ir/health" \
-H "X-Key: YOUR_X_KEY"
3
Chat Completions (OpenAI-compatible)
Send a chat completion request via the gateway.
curl -X POST "https://api.alephbasys.ir/v1/chat/completions" \
-H "X-Key: YOUR_X_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-4o-mini",
"messages": [{"role":"user","content":"Hello!"}]
}'
Frequently Asked Questions
Gateway enforces rate limits; see your plan settings.
Standard HTTP status codes with JSON error bodies.
By default, provide X-Key for all routes; you may exempt docs endpoints in your reverse proxy.
Home
/
Authentication
Authentication
Security First: All API requests must be authenticated with your gateway header key.
X-Key Header Authentication
Provide your gateway key in the X-Key header.
Important: Never expose keys in client-side apps or public repos.
Usage
Example Request
Key Properties
| Property |
Description |
Required |
key |
Your gateway access key (header: X-Key) |
Yes |
scope |
Optional: service scopes configured in gateway |
No |
expires_at |
Optional expiry if you rotate keys periodically |
No |
OAuth 2.0
If your deployments enable OAuth, document here.
JWT Tokens
If your services issue JWTs internally, document here.
Home
/
API Reference
API Reference
Complete reference for your Mana Gateway endpoints (generated from OpenAPI).
/v1/models, /v1/chat/completions, /v1/completions, /v1/embeddings
ASR / Identify / TTS
POST
GET
Speech & speaker endpoints including diarization and TTS.
Home
/
Try It Console
API Console
Send live requests with your X-Key. CORS must allow your origin if using this page locally.
Response
Pending
Response time: —
Response Headers
Response Body