Meldport

xAI models and API pricing

Published xAI models available through Meldport. Check capabilities before selecting a model for your integration.

Latest catalog evidence: Verified on 2026-11-06.

USD per million tokens. List prices are the catalog's published reference rates.
Model / publisherInputOutputList input / outputPublished discountCapabilities / contextEvidence
Grok 4.7
xAI
$0.6$1.8$2 / $6Input: 70%
Output: 70%
text, cache, tools, stream
500K tokens
Verified on 2026-11-06
Expires 2026-11-07
Grok 4.7 Fast
xAI
$1.2$3.6$4 / $12Input: 70%
Output: 70%
text, cache, tools, stream
500K tokens
Verified on 2026-11-06
Expires 2026-11-07
Grok 4.5
xAI
$0.6$1.8$2 / $6Input: 70%
Output: 70%
text, vision, cache, tools, stream
500K tokens
Verified on 2026-11-06
Expires 2026-11-07

Select the exact model and variant

Compare the published context, capabilities and complete model ID before choosing a route. Prices and availability can change; inspect the evidence date on each entry.

One currently active example is Grok 4.7, API ID meldport/grok-4.7. Its published context is 500,000 tokens; published capabilities: text, cache, tools, stream. Evidence checked 2026-11-06. Review the model detail for its current evidence and limits.

Try a bounded Chat Completions request

Send this JSON to POST https://api.meldport.com/v1/chat/completions, with Content-Type: application/json and your dedicated key in the Authorization: Bearer header.

{
  "model": "meldport/grok-4.7",
  "messages": [
    {
      "role": "user",
      "content": "Reply with one short sentence."
    }
  ],
  "max_tokens": 64,
  "stream": false
}

Store a dedicated key in your environment and follow the authentication quickstart. Use the exact ID above; a paid model ID and a :free alias have separate funding rules. See the eligible free aliases and shared monthly pool before assuming a free version is available.

Calculate ordinary input, cache and output costs, compare gateway tradeoffs, or read why your token ratio matters. Client-specific streaming and tool behavior must be tested separately; see agent compatibility.