Report ID MZZR20260918182035B01736Generated at 2026/09/19 02:20
Insufficient evidence to determine
Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.
Insufficient evidenceEvidence status
All primary checks passed in this run.
Tested byMozhenzhen
Tested modelGPT-5.6 Sol
Providersbyesu.net
Requests28
Duration4 min 19 sec
Identity verdictInsufficient evidence to determine
ReferenceNo reference under matching conditions
API and capability checks
The basic API call succeeded and returned a recognizable response.
No issues were recorded in the checks performed. Untested capabilities are outside this conclusion.
API results and model identity are assessed separately. Insufficient evidence does not mean a failed request or a fake model.
Model reference evidence
No reference samples under matching conditions are available for this model.
Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.
Rule version:2026-09-14.v1
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage135.5KThe actual usage reported by the API; this page goes by it.Estimated usage74.9KEstimated from this test's requests.Deviation81% aboveThe reported usage is above the estimate; check your bill.Usage checkAbove the estimateFigures are as reported by the API; your bill is authoritative.
Token cache usage test
Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.
Total 5 request
Share billed at the cache rate72.0%
Low cache share
Caching was used, but only a little; check your bill to see how much it really saves.
Usage this run38.1KCached tokens27.5KNon-cached tokens10.7KAverage per run7.6K
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Long-context test
We test how much it can read at once, then compare that with the officially stated length.
1 tiers
Verified up to 32K
All tested context tiers (32K) returned reliably.
Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.
Test details
Expand any row for details; anything private has been removed.
22 checks
Model list visibility
gpt-5.6-sol is visible in the API model list.
Passed
Test details
This test ran 2 times; result: Passed.
Basic call probe
The basic API call succeeded and returned a recognizable response.
Passed
Test details
This test ran 1 times; result: Passed.
Model self-identification
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
指令跟随
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
JSON 结构
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
标签结构复述
按官方接口的标准调用,看返回是否规范。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 232 tokens
隐藏提示词边界
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
品牌边界
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
用量数据是否完整
核对它报回来的用量和缓存计费。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
逻辑网格推理
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 371 tokens
复测一致性
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
Passed
Test details
This test ran 2 times: 2 passed.
This test used 8.8K tokens
of which 8.4K tokens were billed at the cache price
OpenAI 身份与安全边界
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 3.8K tokens were billed at the cache price
OpenAI 身份与安全边界
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 353 tokens
模型代码锚定
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
Model-family test: series and tier identification
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 3.8K tokens were billed at the cache price
Deep model test: family-specific boundary
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
按官方接口标准调用:OpenAI Responses
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
边打字边回和一次性回,结果一样吗
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
让它调用工具,返回格式对不对
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 165 tokens
让它按指定格式输出,格式兑现了吗
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
连问 5 次,重复内容有没有按缓存价计费
针对这个模型再做一项专门检测。 5 次都对。
Passed
Test details
This test ran 5 times: 5 passed.
This test used 38.1K tokens
of which 27.5K tokens were billed at the cache price
32K 上下文能力实测
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 25.1K tokens
of which 4.2K tokens were billed at the cache price
Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.
Tested byMozhenzhen
Tested modelGPT-5.6 Sol
Providersbyesu.net
Requests28
Duration4 min
Identity verdictInsufficient evidence to determine
ReferenceNo reference under matching conditions
API and capability checks
The basic API call succeeded and returned a recognizable response.
No issues were recorded in the checks performed. Untested capabilities are outside this conclusion.
API results and model identity are assessed separately. Insufficient evidence does not mean a failed request or a fake model.
Model reference evidence
No reference samples under matching conditions are available for this model.
Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.
Rule version:2026-09-14.v1
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage135.5KThe actual usage reported by the API; this page goes by it.Estimated usage74.9KEstimated from this test's requests.Deviation81% aboveThe reported usage is above the estimate; check your bill.Usage checkAbove the estimateFigures are as reported by the API; your bill is authoritative.
Token cache usage test
Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.
Total 5 request
Share billed at the cache rate72.0%
Low cache share
Caching was used, but only a little; check your bill to see how much it really saves.
Usage this run38.1KCached tokens27.5KNon-cached tokens10.7KAverage per run7.6K
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Long-context test
We test how much it can read at once, then compare that with the officially stated length.
1 tiers
Verified up to 32K
All tested context tiers (32K) returned reliably.
Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.
Test details
Expand any row for details; anything private has been removed
22 checks
Model list visibility
gpt-5.6-sol is visible in the API model list.
Passed
Test details
This test ran 2 times; result: Passed.
Basic call probe
The basic API call succeeded and returned a recognizable response.
Passed
Test details
This test ran 1 times; result: Passed.
Model self-identification
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
指令跟随
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
JSON 结构
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
标签结构复述
按官方接口的标准调用,看返回是否规范。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 232 tokens
隐藏提示词边界
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
品牌边界
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
用量数据是否完整
核对它报回来的用量和缓存计费。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
逻辑网格推理
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 371 tokens
复测一致性
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
Passed
Test details
This test ran 2 times: 2 passed.
This test used 8.8K tokens
of which 8.4K tokens were billed at the cache price
OpenAI 身份与安全边界
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 3.8K tokens were billed at the cache price
OpenAI 身份与安全边界
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 353 tokens
模型代码锚定
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
Model-family test: series and tier identification
Asked the model to identify itself; all 1 responses matched the expected name.
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 3.8K tokens were billed at the cache price
Deep model test: family-specific boundary
用几道题看它的回答水平像不像官方模型。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
of which 4.2K tokens were billed at the cache price
按官方接口标准调用:OpenAI Responses
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
边打字边回和一次性回,结果一样吗
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.4K tokens
of which 4.2K tokens were billed at the cache price
让它调用工具,返回格式对不对
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 165 tokens
让它按指定格式输出,格式兑现了吗
对照官方公开的产品说明来测。 1 次都对。
Passed
Test details
This test ran 1 times: 1 passed.
This test used 4.5K tokens
连问 5 次,重复内容有没有按缓存价计费
针对这个模型再做一项专门检测。 5 次都对。
Passed
Test details
This test ran 5 times: 5 passed.
This test used 38.1K tokens
of which 27.5K tokens were billed at the cache price
32K 上下文能力实测
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 25.1K tokens
of which 4.2K tokens were billed at the cache price