Connect xAI/Grok
Create an xAI API key and credits in the xAI console, select a supported Grok model and connect it to Wemblo.
What this guide helps you do
Create an xAI API key and credits in the xAI console, select a supported Grok model and connect it to Wemblo.
Who should use it
Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.
Before you begin
- Use the correct workspace and minimum required role.
- Use a business-controlled provider account where applicable.
- Understand provider billing, usage and data settings.
- Use fictional Pakistan test data.
- Define human handover before enabling automatic replies or calls.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| xAI Console | Provider area for keys and credits. |
| API Key | Secret bearer credential. |
| Credits | Provider-side usage balance. |
| Grok Model | Supported model selected in Wemblo. |
| Usage | Provider and Wemblo activity controls. |
Step-by-step instructions
- Open the official xAI console.
- Sign in with the business-controlled account.
- Purchase or confirm credits where required.
- Choose Create API Key.
- Copy and store the key securely.
- Open Wemblo AI Providers and choose xAI/Grok.
- Paste the key in the protected field.
- Select a supported Grok model.
- Save and test.
- Review usage and credit balance.
- Rotate/revoke the key if exposed.
Test and verification
- Save the provider configuration.
- Run a short fictional customer question.
- Confirm the selected model returns a result.
- Review provider usage and Wemblo AI usage.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Unauthorized | xAI key and account. |
| Credits unavailable | Provider credit balance. |
| Model unavailable | Current xAI model access and Wemblo list. |
| Rate limit | Provider limit and request volume. |
Security, privacy, consent, cost and provider notes
- AI-provider charges and Wemblo AI-action usage are separate controls.
- Do not expose provider keys or customer data in screenshots, tickets or client-side code.
- Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
- Do not promise perfect accuracy or guaranteed business outcomes.
Last reviewed: