EvoLink integration
EvoLink does not currently offer a GPT-6.1 Terra route. Get an alert when access opens.
GPT-6.1 Terra could give developers another option when balancing task quality, execution time, and API costs. The community’s case for a middle tier is specific: smarter and more reliable than the existing Luna model, cheaper and faster than GPT-6.1 Sol.
GPT-6.1 Terra appears in public engineering code. API access through EvoLink is not available yet.
EvoLink does not currently offer a GPT-6.1 Terra route. Get an alert when access opens.
Microsoft’s EF Core evaluation configuration lists gpt-6.1-terra as the default judge model.
OpenAI has not published a GPT-6.1 Terra model page or API specifications.
OpenAI’s API changelog has no GPT-6.1 Terra release entry.
Reports describe a new Terra model with lower pricing than GPT-6.1 Sol. Official pricing and performance details are pending.
Developers discuss a model that could be more reliable than Luna and faster than GPT-6.1 Sol. Some question the need for another tier.
Pre-launch · Updated October 22, 2026
Get an EvoLink email when GPT-6.1 Terra becomes available for evaluation.
Your email is used for EvoLink model availability updates.
Discuss your integration needs: Join the EvoLink community
The request model ID, supported inputs and tools, current route pricing and limits, and how to retain your existing model as a fallback.
Verified public reference
Microsoft’s EF Core repository includes an evaluation configuration that references gpt-6.1-terra as the default judge model.
defaults:
model: ${MODEL=gpt-6.1-sol}
judge_model: ${JUDGE_MODEL=gpt-6.1-terra}
judge_reasoning_effort: ${JUDGE_REASONING_EFFORT=medium}The configuration uses GPT-6.1 Sol for the task and Terra as the judge, with medium reasoning effort. Its defaults can be overridden. EvoLink access is still pending.
Third-party configuration · Unverified
A third-party client lists these values for gpt-6.1-terra. They describe that client’s configuration, not confirmed OpenAI specifications.
| Configuration field | Value listed in the repository |
|---|---|
| Context window | 1,050,000 tokens |
| Maximum output | 128,000 tokens |
| Reasoning levels | low / medium / high / xhigh / max |
| Input types | Image and text |
| Preferred endpoint | Responses API |
Use these workflows to compare Terra with your current models if access opens.
Targeted fixes, bounded implementation work, and routine checks could benefit from a model that follows the requested scope and reaches a usable stopping point quickly.
A larger workflow may contain many well-defined execution steps. Terra could be worth evaluating as a worker model where completion quality, latency, and accumulated cost all matter.
For recurring tasks, small differences in retries and completion time can accumulate. Evaluation should measure consistent results across representative inputs.
| Item | Current status |
|---|---|
| Public development reference | gpt-6.1-terra appears in Microsoft’s evaluation configuration |
| Official API model ID | Pending confirmation |
| Public API access | Pending confirmation |
| Official pricing and limits | Pending confirmation |
| EvoLink availability | Not available yet |
| Release date | No date announced |
Community expectation · Developers want fewer mistakes than Luna on demanding tasks and faster, less costly results than GPT-6.1 Sol.
| Workload consideration | The community’s proposed role for Terra |
|---|---|
| Luna requires too much correction on a task | More dependable execution with fewer retries |
| GPT-6.1 Sol takes longer than the workflow can comfortably accommodate | Shorter time to a usable result |
| Repeated execution makes total costs significant | A lower-cost option with sufficient capability |
| A larger workflow contains many clearly defined subtasks | A practical execution tier for delegated work |
| Public signal | Evidence category | Update |
|---|---|---|
| Microsoft evaluation configurations reference gpt-6.1-terra | Verified | gpt-6.1-terra appears as a judge model. |
| A journalist previews a potential new Terra model | Reported | A new Terra model is under discussion. |
| The journalist revises the release window to the coming weeks | Reported | The earlier “this month” expectation was revised. |
| Developers discuss a tier between Luna and GPT-6.1 Sol | Community expectation | Some want a faster middle tier; others question the need for it. |
Keep model selection configurable so you can evaluate a new route without changing your application’s core logic. Continue using a verified model for current workloads. Leave the Terra candidate unset until its model identifier, endpoint support, and access through EvoLink are confirmed.
export const modelRouting = {
activeModel: process.env.EVOLINK_PRIMARY_MODEL,
fallbackModel: process.env.EVOLINK_FALLBACK_MODEL,
// Set only after Terra access and the exact route are verified.
terraCandidate: process.env.EVOLINK_TERRA_MODEL || null,
};Configuration example. Set EVOLINK_TERRA_MODEL after access and route details are confirmed.
Retain your existing model and fallback configuration while evaluating a newly available route. Compare the candidate against the model your application already uses.
Save examples from your actual workload with clear acceptance criteria. For Terra’s potential role between Luna and Sol, measure completion quality, total task time, retries, and cost per successful result.
Verify the exact model identifier, supported request fields, input types, reasoning settings, and applicable limits. Check usage reporting and billing against the same request records before moving production traffic.
Lower pricing is part of the reported direction for the new Terra model. Official input, output, cached-input, and other applicable rates remain unconfirmed.
For API workloads, the useful comparison will be cost per successfully completed task. A lower token price can lose its advantage when a task requires repeated attempts, additional tool calls, or manual correction. Terra’s pricing case will depend on how much reliable work it completes for the total amount spent.
Community expectation · Some users describe GPT-6.1 Sol as painfully slow, while Luna is inexpensive but prone to mistakes and struggles with larger tasks. GPT-5.6 Terra had fans for being quick, predictable, and able to follow a defined task without endlessly polishing it. That experience explains the interest in a new Terra tier.
Complete defined tasks while preserving important instructions and constraints.
Reduce the time between a request and an acceptable result.
Keep repeated execution affordable without creating excessive rework.
Explore available models through EvoLink’s unified API gateway. Compare capability, completion time, total cost, and operational limits against your production workload.
Start with this documented model for complex coding and professional work; retain measured quality and cost as your comparison baseline.
Explore GPT-6.1 SolEvaluate a current model for focused, high-volume tasks when throughput and cost matter. Check the model page for supported inputs and route prices.
Explore GPT-6 LunaIf you already use GPT-5.6 Terra, keep that exact version as a baseline. Its specifications and price do not transfer to a possible 6.1 model.
Explore GPT-5.6 modelsReview each model’s API specifications and pricing.
Check current access, supported tasks and pricing in the existing model page.
Build a baseline for focused, high-volume workloads.
What is GPT-6.1 Terra? Explore its release timeline, Microsoft's public code reference, and why developers want a different balance of speed and reliability.
Learn how to configure API authentication and send a chat completion request through EvoLink.
No public GPT-6.1 Terra API release has been announced. EvoLink does not offer a Terra route yet.
Reporting points to a lower price than GPT-6.1 Sol. Official rates have not been confirmed.
That is a community expectation prompted by reports of slow GPT-6.1 Sol workflows. GPT-6.1 Terra’s actual task completion times remain to be tested.
The comparison is with the existing Luna model. Users want fewer mistakes and more reliable handling of larger tasks; GPT-6.1 Terra’s results remain to be tested.
That remains to be seen. Compare task quality, completion time, and cost once Terra is available.
gpt-6.1-terra appears in public code, but OpenAI has not listed it as a public API model ID.
Not yet. GPT-6.1 Terra is not available through EvoLink. Join the launch alert for availability updates, or explore the model catalog for current API options.