GPT-6.1 Sol
Review GPT-6.1 Sol model IDs, endpoint, request parameters, and list prices for HopsAPI.
GPT-6.1 Sol is a chat model in the HopsAPI catalog. This page documents only gateway-verified protocols, endpoints, model IDs, and list prices; context length, vision, tools, reasoning, and JSON capabilities depend on the current upstream and live response.
Model information
| Item | Value |
|---|---|
| Protocol | OpenAI Chat Completions; also OpenAI Responses when the model list includes responses_endpoint |
| Endpoint | POST /v1/chat/completions; optional POST /v1/responses |
| Availability | Use the current API key's GET /v1/models response |
| Pricing | Short context $2 input / $10 output per 1M tokens; see Official prices |
Model IDs
| Model ID | Notes |
|---|---|
gpt-6.1-sol | Use this ID when returned by the current API key's model list |
Do not assume that the model is enabled for your account from this page alone. Before calling it,
query GET /v1/models and use the returned model ID, endpoint, and optional
responses_endpoint exactly.
Official prices
Prices are USD per 1M tokens, before your account coefficient. A prompt with more than 400,000 input tokens uses the long-context prices for input, output, and cached input on the whole request, not only the tokens above the threshold. A prompt of exactly 400,000 tokens stays on the short-context prices. Cache writes are not billed on these endpoints.
| Item | Short context | Long context |
|---|---|---|
| Input | $2.00 | $4.00 |
| Cached input | $0.10 | $0.20 |
| Output | $10.00 | $15.00 |
Cached input tokens are a subset of prompt tokens. That portion uses the cached-input price, and the remaining prompt tokens use the input price. See Billing & reconciliation.
Core request parameters
| Parameter | Required | Description |
|---|---|---|
model | Yes | Use an ID above that is returned by the model list |
messages | Yes | Message array in the protocol's native format |
max_tokens | No | Limits model output length |
temperature | No | Sampling parameter; accepted range depends on the current upstream |
stream | No | Use the protocol-specific streaming endpoint or field |
Request example
curl https://hopsapi.com/v1/chat/completions \
-H "Authorization: Bearer sk-YOUR_KEY" \
-H "content-type: application/json" \
-d '{"model":"gpt-6.1-sol","max_tokens":256,
"messages":[{"role":"user","content":"Introduce this model in one sentence."}]}'Response example
This example shows the protocol shape only. Text, token counts, and additional fields such as id and model come from the live response.
{
"choices": [
{
"message": {
"role": "assistant",
"content": "This chat model is called through OpenAI Chat Completions."
},
"finish_reason": "stop"
}
],
"usage": { "prompt_tokens": 16, "completion_tokens": 20, "total_tokens": 36 }
}The gateway passes through native protocol responses and streaming events. Model IDs follow the channel selected for that model on the current API key. See List models, OpenAI Responses API, and OpenAI format.