A dark angled circuit board with red traces, representing a frontier model provider.
Grok sits at the model layer of your stack, reached through an API rather than run on your own hardware.

xAI is the company that builds the Grok family of large language models . Grok is available two ways: as a consumer chat app and as a developer API that you call from your own applications. If you build software that needs to generate text, hold a conversation, use tools, or work with images and voice, xAI is one of several foundation model providers you can wire into your product. This page explains what Grok is, where it fits among frontier model providers, and how you access it.

Where Grok sits in your stack

You do not host Grok. xAI runs the models and exposes them over an HTTP API. Your application sends a request, xAI runs inference , and returns a response. This is the same pattern used by other hosted model providers.

Your app
Backend service Agent or workflow Sends prompts, tool calls, and context
API layer
api.x.ai/v1 OpenAI-SDK compatible Responses, Voice, and Imagine endpoints
Model layer
Grok chat models Grok coding model Image and voice models
Infrastructure
xAI compute Managed by xAI, not by you

How to access it

There are two front doors.

Consumer app. Grok is available as a chat product for end users. This is the fastest way to try the model with no code, useful for evaluating tone and behaviour before you commit to an integration.

Developer API. For product work, you use the xAI API. The base endpoint is https://api.x.ai/v1. According to the official docs, the API is compatible with OpenAI’s client library, so you point the OpenAI SDK at the xAI base URL and pass an xAI API key as a bearer token. That compatibility matters: if your code already targets an OpenAI-style client, switching to Grok is mostly a configuration change rather than a rewrite.

The API groups its capabilities into a few families:

  • Responses API - generate text, hold conversations, and call functions and tools.
  • Voice API - text-to-speech, speech-to-text, and real-time voice.
  • Imagine API - generate and edit images, and generate video from text or images.

xAI documents several models. Grok 4.3 is presented as the default recommendation for chat and coding, alongside reasoning, non-reasoning, and multi-agent variants, plus a smaller coding-focused model. Check the official models page for the current list and specifications before you build, because the lineup changes.

Step 1 Get a key Create an account and generate an xAI API key.
Step 2 Point your client Set the base URL to api.x.ai/v1 in an OpenAI-compatible SDK.
Step 3 Pick a model Choose a Grok model that fits the task, chat, reasoning, or coding.
Step 4 Send requests Call the Responses API with prompts, tools, or images.

How it compares

Grok is one of four frontier model families you will weigh most often. The others are OpenAI’s GPT models, Anthropic’s Claude models, and Google’s Gemini models. They cover similar ground: text generation, tool use, code, and multimodal input. The differences that matter for a buyer are ecosystem, integration surface, and how each provider is packaged in the clouds you already use.

xAI GrokOpenAI GPTAnthropic ClaudeGoogle Gemini
MakerxAIOpenAIAnthropicGoogle DeepMind
Consumer appGrokChatGPTClaudeGemini
API styleOpenAI-SDK compatibleNative OpenAI SDKAnthropic SDKGoogle SDK
Cloud packagingAlso via third-party cloudsAzure OpenAIAmazon Bedrock, othersGoogle Cloud
Best forTeams wanting an OpenAI-style swap-inBroad ecosystem and toolingLong-context reasoning workGoogle Cloud shops

The OpenAI-compatible surface is Grok’s most practical selling point for engineering teams: you can trial it against existing code with little friction. For a wider view of how the model market fits together, see the LLM landscape for 2026 and the head-to-head on Claude versus ChatGPT .

When not to use it

Grok is not always the right pick.

  • You need a specific cloud’s contract and controls. If your procurement, data residency, or billing has to sit inside one cloud, a model packaged natively there, such as Azure OpenAI or a model on Amazon Bedrock , may be the cleaner fit.
  • You have standardised on another SDK and ecosystem. If your team already runs deeply on Anthropic’s Claude or another provider, the migration cost can outweigh the benefit of switching.
  • You require a capability Grok does not document. Match your requirements to the official model and API docs. Do not assume a feature exists.
  • You need reproducible, benchmarked evidence for a regulated use case. Run your own evaluation against your tasks rather than relying on marketing claims. See how AI models are evaluated .

Further reading

Sources