Apiporter · GPT 6.1 SolAuthenticity, speed and price analysis

⇆ Compare Visit website

ModelCodex_coreData security level 018 samples

AuthenticityNot tested

Consistency Not tested · Dilution Not tested

—Model consistency score

Speed#2 / 7

First token 2.45 s · Output speed Not provided

2.45First token
(seconds)

Price—

Input — · Output — · Cache discount Not provided

—Cost per
coding session

Availability#3 / 7

7 days 100.0% · 30 days 100.0%

100.0%Last 24 hours
availability

Comparison summary

GPT 6.1 Sol on Apiporter: availability over the last 24 hours is 100.0%, ranking 3 of 7 relays with data (median 100.0%); time to first token is 2.45 s, ranking 2 of 7 (median 4.67 s).

Authenticity checks (model consistency and dilution) are not live yet; once they are, this section will compare the relay with the official API.国内正规企业，任意金额可开票、在线客服系统、多渠道聚合站、高可用性

Authenticity

Model consistency

Output distribution for the same requests on this relay and on the official API · higher is better

Once authenticity checks are live, this shows the distribution distance from the official API, capability-question pass rates side by side, and usage count drift. Routes that fail are greyed out on every leaderboard, with the reason shown in red on hover.

ⓘ Method: see the blog post “Did the model really get dumber?” Read

Speed

Measured by time to first token (seconds) and output speed (tokens / second)

Time to first token

Seconds until the first token · lower is better

7 relays

ⓘ Output speed: not yet available from the live API; shown once connected

Price

Cost per coding session

GPT 6.1 Sol · 2M input and 40k output tokens (¥) · split by token type · lower is better

3 relays

OutputInput

ⓘ USD prices are converted at 1 USD = 6.7698 CNY

Prices: cache hit, input and output

¥ / 1M tokens

Cache hitInputOutput

Cache

Coding requests repeat much of their context, so the cache hit rate largely decides what you actually pay. Drag the hit rate and the costs and ranking below are reweighted with cache prices.

Cache discount

Not provided

Cache hit — · input — (per 1M tokens)

Measured hit rate

Pending

Measured by replaying multi-turn sessions: cached-read tokens in usage as a share of all input

Session cost at 80% hit rate

—

Cache-weighted session cost

GPT 6.1 Sol · of 2M input tokens, the hit share is billed at the cache price and the rest at the input price, plus 40k output (¥) · lower is better

3 relays

Cache hit rate80%Coding agents typically see 70%–90%

Cached inputUncached inputOutput

ⓘ Routes without a cache price are billed at the input price; cache write fees are not included

Stability

Availability

Request success rate, last 24 hours · higher is better

7 relays

Status of each model, last 24 hours

One cell per hour · green ok, yellow delayed, red failed

Model	Group	Availability	Last 24 hours	First token	Samples
Claude Fable 5.1	Claude_core	100.0%		2.17 s	18
GPT 6 Astra	Codex_core	100.0%		2.88 s	18
GPT 6.1 Sol	Codex_core	100.0%		2.45 s	18
Claude Opus 5.5	Claude_core	100.0%		2.03 s	18
GPT 6 Sol	Codex_core	—		—	0
GPT 5.6 Sol	Codex_core	—	None yet	—	—

Service details

Minimum top-up¥5

Sign-up bonus¥0.4

Support response工作日内1小时

Payment methodsAlipay, Other

China invoiceSupported

International invoiceNot supported

RefundsContact required

Promotions无

Strengths

起充较低，并且支持任意金额可开票

Limitations

增强claude模型的稳定性，减少443出现

FAQ

How much does GPT 6.1 Sol cost on Apiporter?

No public price yet.

How does the cache hit rate affect price?

Apiporter has not published a cache price for this route, so cache hits are billed at the input price.Measured hit rates will replace this assumption once available.

Which models does Apiporter support?

Folkbench currently lists 6: GPT 6 Astra, Claude Fable 5.1, GPT 6 Sol, GPT 6.1 Sol, Claude Opus 5.5, GPT 5.6 Sol.

What does the data security level mean?

Folkbench rates relays from 0 to 4 based on public policies and verifiable evidence; Apiporter is currently level 0. The check covers leaks in responses and error messages only, and does not prove data retention or training policies.

How often is this data updated?

Availability and time to first token use a 24-hour window, and this page syncs live data every 15 minutes.