Explore Franklin AI

GPT-6.1 Sol vs GPT-6.1 Terra: benchmarks and token cost

Compare GPT-6.1 Sol (Max) vs GPT-6.1 Terra (Max) with benchmark results, speed, pricing, and practical workflow guidance.

Best For GPT-6.1 Sol (Max)

  • Evaluate this exact variant against a fixed set of representative tasks.

Best For GPT-6.1 Terra (Max)

  • Compare accepted-result cost and latency under the same task requirements.

Comparing two rate tiers within GPT-6.1. Compare the captured model variants, overall index, token pricing and response metrics.

This comparison uses GPT-6.1 Sol (Max) and GPT-6.1 Terra (Max). It reports the captured benchmark data, with no new hands-on test.

Comparing two rate tiers within GPT-6.1

Sol records 54.5 on the captured intelligence index and Terra 51.0. Terra’s listed input and output rates are half Sol’s. This is a useful pair for a controlled quality-versus-cost test within one provider family. Keep request settings and grading fixed, and count retries or escalations when estimating the lower-rate option’s effective savings.

How to read the table

The intelligence index is an aggregate measurement, not a percentage of correct answers in your application. Input and output prices are separate rates per million tokens. Coding and math indices are unavailable in this capture and must not be read as zero. Compare first-token latency separately from output-token throughput, and use the same model effort settings for a trial. Choose using task quality, total time and the cost of accepted results; provider features and deployment requirements need their own checks.

Benchmark table

Scores, speed, and pricing captured for this analysis. Open a model page for the latest results.

Metric OpenAI GPT-6.1 Sol (Max) OpenAI GPT-6.1 Terra (Max)
Index Scores
Intelligence Index 54.5 51.0
Coding Index--
Math Index--
Benchmark Scores

Verdict

Sol records 54.5 on the captured intelligence index and Terra 51.0. Terra’s listed input and output rates are half Sol’s. This is a useful pair for a controlled quality-versus-cost test within one provider family. Keep request settings and grading fixed, and count retries or escalations when estimating the lower-rate option’s effective savings.

Comments (0)

No comments yet

Be the first to share your thoughts!