Use your own xAI key
Connect Grok with your own XAI_API_KEY. TEKIZ.AI
does not proxy xAI sign-in sessions or grant Grok access.
OpenAI-compatible setup
Point OpenAI SDKs, Codex, Cursor, Aider, Continue, OpenHands, and
compatible apps at https://api.tekiz.ai/v1. TEKIZ.AI
Router can use Grok or another model you connected.
Keep working when an account is busy
When a Grok key or model is rate-limited, TEKIZ.AI can try another model you are allowed to use. Your apps do not need their own retry setup.
Set up xAI Grok setup
export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_tekiz_your_generated_key
export XAI_API_KEY=xai-your_authorized_key
curl "$OPENAI_BASE_URL/chat/completions" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "tekizai/frontier",
"messages": [{"role": "user", "content": "Use Grok if it is the best healthy authorized route"}]
}'
Use more than one xAI key
Add multiple authorized xAI keys. TEKIZ.AI shares requests across keys that are working and pauses only the key that fails.
Send files to services that accept them
Images, audio, video, and documents are sent only to models that can handle that kind of input.
Use accounts you are allowed to use
TEKIZ.AI plans provide routing, API keys, usage limits, and request history. They do not include xAI access or proxy xAI sign-in sessions.
Why put TEKIZ.AI in front of Grok?
Grok is a useful frontier model, but keys can hit limits and services can go offline. TEKIZ.AI checks which keys and models are available, sends files to compatible models, and keeps local or cloud backups ready.
Next steps
Create an API key, copy the hosted quickstart, use the OpenAI-compatible setup, or estimate routing fit.
Stay within your approved services
If your company approves only xAI, keep that boundary. TEKIZ.AI can reduce token burn while making better use of existing subscriptions and account billing.