Use GPT-6.1 Sol API for text generation: Q&A, coding, documents and agent workflows. Try it online and view pricing and Responses examples.
Provider: OpenAI
Category: text generation
Endpoint: /v1/responses
Status: Available
Cost: --
API access
Endpoint
POST /v1/responses
Base URL
https://api.hiapi.ai
Uses the OpenAI Responses format. One HiAPI key works across all available models.
Input price
1,000 Credits
/ 1M tokens · Total input ≤ 272,000 tokens
Output price
5,000 Credits
/ 1M tokens · Total input ≤ 272,000 tokens
Context
1.05M
context window
Max output
128K
output tokens
Try GPT-6.1 Sol
Ask a question to stream the answer and inspect token usage, latency, and estimated cost.
GPT-6.1 Sol API Quickstart
Call GPT-6.1 Sol with the streaming OpenAI Responses format. Copy a ready-to-use cURL, Python, or Node.js example below.
/v1/responsescurl -N -X POST "https://api.hiapi.ai/v1/responses" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-6.1-sol",
"input": [
{
"type": "message",
"role": "user",
"content": [
{
"type": "input_text",
"text": "A cat walking on the beach at sunset"
}
]
}
],
"stream": true,
"store": false,
"reasoning": {
"effort": "medium"
}
}'Tip: Replace YOUR_API_KEY with your actual API key from the API Keys page.
Uses the OpenAI Responses format. Keep stream: true, send input as a message array, and set reasoning effort with reasoning.effort.
Responses API
Request fields at a glance
Start with core fields, then enable advanced capabilities as needed.
Core fields
The fields that form a valid request
- model Required
- Use the model ID shown on this page.
- input Required
- Pass the current conversation context as a message array.
- stream Required
- Must be set to true.
- store Fixed
- Fixed to false and shown explicitly in examples.
Capability fields
Enable reasoning, context, and tools as needed
- reasoning.effort Optional
- low, medium, high, xhigh, max. Examples and Playground default to medium; set this field explicitly in API requests.
- instructions Optional
- Define the role and response requirements.
- previous_response_id Conditional
- Use with compatible storage and response chaining; with store=false, replay context from the client.
- tools / tool_choice Optional
- Declare and control function tool calls.
Max output is a model specification limit, not a per-request generation target. Examples show only the runtime fields currently available and verified on HiAPI.
GPT-6.1 Sol API Pricing
Billing follows the input, output, and cache token categories actually reported in usage. All prices below are shown per 1 million tokens.
Total input ≤ 272,000 tokens
- Input tokens
- 1,000 Credits/ 1M tokens
- Output tokens
- 5,000 Credits/ 1M tokens
Prompts and context sent to the model
Responses and reasoning generated by the model
- Cache read
- 50 Credits/ 1M tokens
- Cache write
- 1,250 Credits/ 1M tokens
Long-context pricing and billing details
The tier is selected by total input tokens per request, including cache reads and writes. Above the threshold, that tier applies to all input, output, and cache tokens in the request, not only the excess.
| Token type | Total input ≤ 272,000 tokens | Total input > 272,000 tokens |
|---|---|---|
| Input | 1,000 Credits | 2,000 Credits |
| Output | 5,000 Credits | 7,500 Credits |
| Cache read | 50 Credits | 100 Credits |
| Cache write | 1,250 Credits | 2,500 Credits |
All prices are per 1 million tokens.
GPT-6.1 Sol Model Specifications
These specifications reflect the current public HiAPI text request contract. Undisclosed capabilities are not inferred by the page.
- Streaming
- Supported
- Tool calling
- Supported
- Structured JSON
- Supported
- Reasoning
- Supported
- Input modalities
- text
- Output modalities
- text
- Reasoning efforts
- low · medium · high · xhigh · max
- Max output
- 128K
About GPT-6.1 Sol
Use GPT-6.1 Sol API for text generation: Q&A, coding, documents and agent workflows. Try it online and view pricing and Responses examples.
HiAPI exposes this model through /v1/responses. Test prompts and parameters in the Playground, then use the same HiAPI API key in your server application.
- Provider
- OpenAI
- Endpoint
- /v1/responses
- Context window
- 1.05M
- Released
- Not disclosed
How to Use GPT-6.1 Sol
The Playground and API share the same model ID, so three steps take a tested prompt into production.
Step 1
Validate online
Test instructions, input, and reasoning.effort in the Playground.
Step 2
Manage API keys
View an existing key or create another after signing in; one key works across all available models.
Step 3
Integrate your server
Send requests to /v1/responses and track cost with the usage object.
Frequently asked questions
What is GPT-6.1 Sol suited for?
GPT-6.1 Sol is an OpenAI text model for coding, analysis, research, and tasks that benefit from multistep reasoning. This page describes the streaming Responses text integration; image, audio, and video input or output are outside this integration.
Which model ID and endpoint should I use?
Use model ID gpt-6.1-sol with POST /v1/responses. The request must use an input array, stream=true, and store=false.
Which reasoning.effort values are supported?
The current HiAPI integration supports low, medium, high, xhigh, and max. Examples and Playground default to medium; send reasoning.effort explicitly when you need a fixed setting. Other values are not part of this model contract.
Why are temperature, top_p, and max_output_tokens unavailable?
The current GPT-6.1 Sol integration contract does not expose these fields. Omit them and use reasoning.effort when you need to change reasoning depth. Do not copy sampling parameters from another model into this request.
How should I process the stream?
Read SSE events by type and accumulate response.output_text.delta. Finish on response.completed, response.incomplete, or response.failed. Do not parse the whole stream as one JSON object or rely only on output in the completion event.
How do I continue a conversation with store=false?
Keep the required user messages, assistant items, and tool items in your client, then replay them in the next input array. Replayed history counts as input again; use usage details to determine cache reads and writes.
How are input, cache, and output tokens billed?
Input, cache reads, cache writes, and output use the live token rates shown on the model page. Count a cache read or write only when usage reports cached_tokens or cache_write_tokens; both are included in the input total and must not be added twice. reasoning_tokens are already included in output_tokens and must not be added again; settled charges are recorded in account usage logs.
How does pricing work above 272K input tokens?
The tier uses total input tokens for the request, including cache reads and writes reported in usage. Up to 272,000 input tokens uses the standard tier; from 272,001, the long-context rates apply to the whole request, including input, output, and cache, rather than only the excess.
What should I check when a request fails or has no text?
Check the API key, model, Responses endpoint, input array, stream=true, and store=false first. For missing text, verify that the client handles SSE deltas; for cost questions, compare input_tokens, cached_tokens, cache_write_tokens, and output_tokens in usage.
HiAPI Blog
