Contacting Sales and Grok for Business

An enterprise offer that isn’t self-service

You can get standard xAI API access in minutes at console.x.ai: create an account, generate a key, and send your first request right away. The Enterprise offer doesn’t work that way. It requires contacting the xAI sales team, and this difference isn’t just a gratuitous bureaucratic hurdle. Everything that makes the Enterprise tier valuable—reserved capacity, negotiated pricing, contractual commitments, choice of processing region—involves elements you discuss and sign off on, not check boxes in a payment form. Two channels open this discussion, and they serve slightly different situations.

The Grok for Business form

The x.ai/grok/business page is the recommended entry point. It presents the benefits of the Enterprise offer and provides a structured contact form that asks you to describe your use case and volume needs, indicate your organization size, specify compliance requirements specific to your industry, and optionally request a customized demonstration.

This structured format works in your favor. A request that immediately mentions a sector subject to GDPR and an estimated monthly volume lands directly with the representative capable of answering it, whereas a vague message triggers an extra qualification back-and-forth before the useful conversation begins. The xAI sales team typically gets back to you within a few business days with a tailored proposal.

Direct contact by email

For more specific requests or technical discussions, the address [email protected] puts you in direct contact with the team. This channel suits negotiations on pricing for large volumes and requests for a proof of concept before commitment.

It’s also the right choice whenever integration touches unusual existing infrastructure—a partially isolated environment, a network routing constraint—or when a specific contract clause needs discussion. A legal department that wants to modify a liability cap before even starting the technical part will naturally go this route rather than using the form.

What to gather before writing

Whichever channel you choose, the quality of the response depends directly on what you put in the initial request. Start by formulating your use case functionally: what you aim to accomplish, for whom, and how often. Then gather the numerical data for the file.

• Estimated volume: tokens per month, input and output counted separately
• Desired models: grok-4.5, grok-4.3, grok-4.20, or a combination
• Technical constraints: maximum acceptable latency, required availability
• Compliance requirements: GDPR, HIPAA, SOC 2, data residency

The input/output separation is worth noting, as it’s the most common mistake at this stage: these two volumes don’t bill at the same rate and don’t provision the same way. If you don’t have measurements yet, take a representative sample of your prompts and expected responses, then extrapolate.

Finally, add your timeline, meaning your target production date. This determines the order in which topics get addressed on your end.

Grok for Business and Enterprise API: two complementary offers

Confusion between these two products comes up constantly in scoping meetings. Grok for Business gives your teams access to Grok via the grok.com web interface, with centralized account and permission management: it’s the tool your marketing leadership or legal department will use daily, without writing a line of code. The Enterprise API offers programmatic access to Grok models, with provisioned throughput, SLA, and enhanced compliance: it’s what your developers integrate into your applications.

You don’t have to choose. A common configuration sees business teams working in Grok for Business for their direct interactions while the Enterprise API powers internal applications, each billed and governed according to its own logic.

The path to activation

Subscription follows a fairly stable path from one file to the next. The first contact, via the form or [email protected], leads to a qualification phase where a sales rep seeks to understand your real needs. Next comes the proposal, in the form of a custom quote with negotiated rates, then the legal review, during which your teams examine the contractual conditions, the DPA, and the Enterprise Terms of Service (ToS). Activation then sets up the Enterprise account with the requested configurations, and an onboarding phase supports you technically on integration.

In practice, the legal review dictates the actual timeline. Qualification and proposal play out in days; contract review plays out in weeks, especially if your data protection officer (DPO) sees the file only when asked to validate it. Loop them in at first contact, using the documents the next lesson presents, and you’ll recover most of the time this type of project usually loses.

Key takeaways

• The Enterprise offer isn’t self-service: contact [email protected] or use the form at x.ai/grok/business
• Prepare your volume estimates, use cases, and compliance requirements before contacting
• Grok for Business (web interface) and Enterprise API (programmatic access) are complementary
• The subscription process includes a qualification phase and contract negotiation