GPT88 / API Docs
ChatxAIFeatured1 vendors

grok-4.6

GPT88 featured Grok route for coding agents, bug investigation, and long-running tool workflows.

Get API Key on gpt88.ccQuickstart

Overview

  • Grok 4.6 is currently featured in the GPT88 catalog for coding, bug investigation, long-running agents, and complex tool workflows.
  • The GPT88 review summary records an Artificial Analysis Intelligence Index score of 61, Terminal-Bench v2.1 at 88.4%, and GDPval-AA v2 Elo at 1753. These are third-party notes dated August 13, 2026, not official GPT88 performance guarantees.
  • If a task requires the model to run commands, inspect results, repair issues, and continue across multiple stages, Grok 4.6 is a useful candidate for a workload-specific evaluation.

Best Use Cases

  • Analyze codebases, investigate bugs, repair tests, and make multi-file engineering changes
  • Run long-running agent workflows with repeated tool calls, terminal operations, and failure recovery
  • Prototype interactive webpages, visual interfaces, and ambitious frontend workflows
  • Compare an execution-quality route with the lower-cost DeepSeek V4 Pro path on the same task set

Integration Notes

  • Use the GPT88 Base URL https://api.gpt88.cc and set model to grok-4.6 in OpenAI-compatible requests.
  • Call GET /v1/models to confirm that the current API key can access grok-4.6 before adding tools, long context, or streaming.
  • Keep the codebase, prompts, tool permissions, and acceptance criteria fixed while recording success rate, end-to-end time, rework, and actual usage.
  • If a client model picker does not list Grok 4.6, use its custom model ID option with the OpenAI-compatible configuration.

Usage Notes

  • Availability, pricing, context limits, rate limits, routes, permissions, and tool support are determined by the current GPT88 console configuration.
  • Public benchmark results depend on model versions, prompts, tools, timeouts, and scoring implementations; they should not be treated as a direct business success-rate forecast.
  • Long-running agents still require code review, permission isolation, tests, logs, and human acceptance. A task completing once is not the same as production readiness.
  • Use a staged rollout and keep a validated fallback model route until the behavior is established on your own workload.

Capabilities

Coding agentsBug investigationLong-running executionInteractive and visual tasks

Recommended Scenarios

  • Codebase analysis
  • Terminal tool use
  • Complex debugging
  • Frontend and interaction prototypes

Endpoint Path

POSThttps://api.gpt88.cc/v1/chat/completions

The endpoint path is determined by the model category. Chat, image, video, and audio models use different endpoints.

Send requests with Authorization: Bearer <API_KEY>. See Chat Completions API for the full parameter reference.

API Docs

Endpoint
POST /v1/chat/completions
Model ID
grok-4.6
Content-Type
application/json
Protocol
OpenAI-compatible chat completions endpoint with streaming and non-streaming output.
Base URL
Use https://api.gpt88.cc for OpenAI-compatible and Claude-style tools.

Headers / Auth

  • AuthorizationstringRequired
    Send Bearer <GPT88_API_KEY>. Create the API key in the gpt88.cc console.
  • Content-TypestringRequired
    Request body format. Audio transcription uploads use multipart/form-data.
    Default:application/json
  • Acceptstring
    Non-streaming requests return JSON; streaming chat requests return SSE chunks.
    Default:application/json or text/event-stream

Chat Protocol Differences

For chat models, the protocol used by the client matters as much as the model name. Claude Code / Anthropic SDK and OpenAI SDK build different request paths.

OpenAI CompatibleRecommended
Base URL
https://api.gpt88.cc
Endpoint
POST /v1/chat/completions
Body
{ "model": "grok-4.6", "messages": [...] }
Anthropic / Claude
Base URL
https://api.gpt88.cc
Endpoint
POST /v1/messages
Body
{ "model": "grok-4.6", "messages": [...] }

This model is usually best accessed through the OpenAI-compatible protocol. Only use the Anthropic-style path when the target tool explicitly requires it.

Request Parameters

The fields below are generated by model category. Pricing, context limits, rate limits, and available routes should be confirmed in the gpt88.cc console.

  • modelstringRequired
    Current model ID: grok-4.6. Preserve the exact casing when copying.
  • messagesarray<Message>Required
    Conversation history. Each message includes role and content.
  • streamboolean
    Enable SSE streaming. Useful for chat interfaces and long responses.
    Default:false
  • temperaturenumber
    Sampling temperature. Higher values produce more variation; production workloads usually start with a fixed value.
    Default:1
  • max_tokensinteger
    Maximum output tokens for this request. Real context limits should be confirmed in the console.
  • response_formatobject
    Structured output config, for example { "type": "json_object" }.
  • toolsarray<Tool>
    Function-calling tool definitions. Availability depends on the model and account configuration.

Response Fields

Response bodies generally follow OpenAI-compatible shapes. Media models may return async task IDs or resource URLs.

  • idstringRequired
    Unique completion ID for tracing and debugging.
  • objectstringRequired
    Usually chat.completion or a streaming chunk type.
  • modelstringRequired
    Actual model ID that handled inference.
  • choicesarray<Choice>Required
    Generated choices including message, delta, and finish_reason.
  • usageobject
    Token usage statistics. Streaming calls may return this only at the end or in non-streaming mode.

Status Codes

  • 200OKRequired
    Request succeeded. See the response field table above for the response body shape.
  • 400Bad Request
    Invalid request fields, such as missing required fields, unsupported image size format, or unsupported file type.
  • 401Unauthorized
    API key is missing, invalid, or malformed.
  • 404Not Found
    Endpoint or model not found. Confirm the path is /v1/chat/completions and the model ID is grok-4.6.
  • 429Rate Limited
    Rate limit, concurrency cap, or insufficient balance. Check the console for the current allowance.
  • 5xxUpstream Error
    Upstream or request failure. Retry with the same Base URL and keep the request ID for debugging.

Errors and Troubleshooting

  • 401: verify Authorization is Bearer <API_KEY> and the key is still valid.
  • 404: confirm the endpoint is /v1/chat/completions and the model ID grok-4.6 is available in the console.
  • 429: reduce concurrency, shorten requests, or check balance and quota in the console.
  • 5xx: retry with the same Base URL and keep the request ID for debugging.

Request Examples

curl https://api.gpt88.cc/v1/chat/completions \
  -H "Authorization: Bearer $GPT88_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "grok-4.6",
    "messages": [
      {"role": "user", "content": "Introduce gpt88.cc in one sentence."}
    ]
  }'

Expected response (trimmed example):

200 OKjson
{
  "id": "chatcmpl-grok-4-6",
  "object": "chat.completion",
  "created": 1730000000,
  "model": "grok-4.6",
  "choices": [
    {
      "index": 0,
      "finish_reason": "stop",
      "message": { "role": "assistant", "content": "..." }
    }
  ],
  "usage": { "prompt_tokens": 24, "completion_tokens": 64, "total_tokens": 88 }
}