Strengths
- 500K-token context
- Function calling and structured outputs
- Reasoning effort low to xhigh
- US data-residency endpoint
Best For
- Software engineering
- Long agentic tasks
- Professional knowledge work
Run It in EDDI
The fastest route is the Manager: open the agent wizard or the Platform Operator and pick the provider and model. To configure it yourself, follow these steps for the provider you want.
xAI · type: "xai"
Model ids: grok-4.7, grok-4.6, grok-4.3
1. Store the credential
Add the provider's API key to the Secrets Vault in the Manager, or with PUT /secretstore/secrets/default/xai-key, under the name used below. Configurations reference it as ${vault:…}, so the key never appears in plain text.
${vault:xai-key}2. Configure the LLM task
Use this as the langchain.json of the agent's workflow, or paste the parameters into the LLM editor in the Manager.
{
"tasks": [
{
"actions": [
"send_message"
],
"id": "chat",
"type": "xai",
"parameters": {
"apiKey": "${vault:xai-key}",
"modelName": "grok-4.7",
"systemMessage": "You are a helpful assistant",
"addToOutput": "true"
}
}
]
}Or create the whole agent in one call
setup_agent writes the rules, LLM configuration and workflow, then deploys the agent. Call it over MCP or POST /administration/agents/setup.
setup_agent(
agentName: "My grok-4.7 agent",
systemPrompt: "You are a helpful assistant.",
provider: "xai",
model: "grok-4.7",
apiKey: "${vault:xai-key}"
)Notes for EDDI
- Set
"region": "us"for xAI's US data-residency endpoint. It serves grok-4.7 and grok-4.6 only.
Related Models
Sources
The facts on this page come from the vendor's documentation, checked on 2026-09-30. Models change quickly, so confirm limits with the vendor before you rely on them. Prices are not listed here: see the vendor's pricing page.