Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Supported API features and tools
A 1,000,000-token context with text and image input
Configurable reasoning, including none for no reasoning
Function calling for integrated tool workflows
Structured outputs for schema-based responses
Batch API support with a published 20% token discount
Before you choose
A large context is not a guarantee of complete recall or correct answers. Provide source labels and ask for traceable evidence.
The reviewed card does not verify a separate maximum output or training cutoff. Do not substitute the context size for either.
The card lists xhigh as well as none, low, medium and high; older prose lists fewer levels. Verify settings against the current card and endpoint.
Text/image input produces text output. Search or other actions require configured tools and do not become available just by selecting the model.
Choose the reasoning effort
nonelow · defaultmediumhighxhigh
The current model card lists none, low, medium, high and xhigh, with low as the default. None switches reasoning off. Some older overview prose lists only four levels; use the current model card when checking availability, and evaluate the cost and latency of each setting on your workload.
Use the exact grok-4.3 ID to make model selection explicit; grok-4.3-latest is a documented alias.
Do not carry reasoning defaults across generations: 4.3 defaults to low, while 4.5, 4.6 and 4.7 default to high.
Function calling describes requests to tools, not permission to execute them. Authorize side effects in your integration and validate structured responses before consuming them.
Put it to work
Start with a more useful prompt.
Original examples from EZ Ai Assist. Adapt these to your task and the features available in your workspace.
Workflow 01
Extract a review checklist
Convert a long policy document into traceable review steps.
Using the policy document below, produce a checklist for reviewing this proposed workflow. For every item, cite the section that creates the requirement, state the evidence a reviewer should inspect, and mark it required or advisory only when the source supports that distinction. Flag contradictory or missing requirements rather than inventing a rule.
Workflow 02
Map requirements to a design
Find gaps between a specification and the proposed implementation.
Compare these numbered requirements with the design document. Create a table with requirement ID, supporting design section, coverage status and an acceptance test. Mark unsupported claims as unverified. Identify dependencies and the smallest clarification needed for each gap, without expanding the product scope.
Workflow 03
Review interface consistency
Use multiple screenshots as evidence without assuming hidden interactions.
Compare these screenshots from the same product. Identify inconsistent labels, spacing, hierarchy and status messaging that are visible in the images. Group repeated issues and suggest minimal changes that preserve the existing branding. For anything requiring keyboard or interactive testing, describe the check instead of claiming the screenshot proves the behavior.
Developer reference
xAI API pricing
These are global xAI API reference prices, not EZ Ai Assist subscription prices.
At 200,000 prompt tokens or more, higher rates apply to the entire request, including its output. A 1M context does not mean 1M tokens at the short-context rate.
The model card lists Batch support with a 20% discount on token rates. This table shows standard processing, not Batch or Priority pricing.
Reasoning usage is billed. Enabled tool charges are additional; X Search bills fetched posts and profiles, including qualifying parent or quoted posts.
Priority processing charges 2× when the response confirms the priority tier. Confirm the exact model, cache hits and enabled tools before estimating total cost.
Common questions
A few things worth knowing.
Why choose Grok 4.3 for a workflow?
It combines a 1M-token context, tool calling, structured outputs and configurable reasoning. Document-heavy extraction and instruction-driven work are useful evaluation cases. Test it against representative inputs rather than treating the context size as a quality ranking.
Can reasoning be disabled?
Yes. The current card lists none, low, medium, high and xhigh; low is the default. None disables reasoning. Older overview prose lists fewer levels, so confirm the card and exact endpoint before relying on a setting.
Does 1M context mean 1M output tokens?
No. The model card establishes a 1,000,000-token context window, not a separate output allowance. A maximum output limit and training cutoff are not verified in the reviewed sources. App limits may be smaller.
Does it support screenshots and structured data?
The card lists text and image input, text output and structured outputs. You can request schema-shaped results through the appropriate integration, but the data and claims still require validation.
How does long-context pricing change the cost?
The standard rates below 200,000 prompt tokens are $1.25 input, $0.20 cached input and $2.50 output per million. At or above 200,000, all three rates double for the request. Tools and reasoning usage also matter.
Is Batch processing available?
Yes. xAI lists Batch API support and a 20% token discount for this model. Batch is asynchronous, not an interactive speed option; eligibility and request details should be checked before integration.
Does this page establish app feature availability?
No. It documents xAI API behavior and prices, not a promise of identical EZ Ai Assist controls, tools or limits. Check the app and plan details before building a workflow around a particular capability.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.