Is gpt-5.6-sol genuine? Deep check result

Report ID MZZR2026081704391656FE78Generated at 2026/08/17 12:39

Matched

gpt-5.6-sol 本次深度验真结果：Matched（86/100）。主要问题：这家接口当时太忙；有检测项没Passed。

86Model consistency score

主要问题：这家接口当时太忙；有检测项没Passed。

Tested byMozhenzhen

Tested modelGPT-5.6 Sol

Providersleyanshi.me

Requests16

Duration1 min 11 sec

Identity verdictVerified

ReferenceCPA 官方产品源

A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。

This call did not complete

Reason for failure

The provider was busy and could not process the request.

What to do

Try again later. Contact the provider if this persists.

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage253.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation85% belowThe reported usage is below the estimate, possibly because of how tokens are counted or compressed.Usage checkBelow 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 1 request

Share billed at the cache rate--

No usage record

This provider's endpoint does not report usage reliably; check it against your bill.

Usage this run0Cached tokens0Non-cached tokens0Average per run0

Usage reportedNot reportedCache billingDid not happenResultHigh risk

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.

5 tiers

Verified up to 200K

400K Failed，原因：接口鉴权或权限异常。

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200K / 400KTests begin at the longest generated context and step down to verify stable, correct responses.

Current guidance

The 400K tier did not return reliably this time; do not rely on this length.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched86/100

主要问题：这家接口当时太忙；有检测项没Passed。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly8 / 12

这家接口当时太忙（隐藏提示词边界） -4

Is it the model it claims to be18 / 18

No deductions

Does it answer like the official model25 / 25

No deductions

Is usage and billing reasonable10 / 10

No deductions

Will it keep working15 / 25

这家接口当时太忙（隐藏提示词边界） -8有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed.

26 checks

Model list visibility

gpt-5.6-sol is visible in the API model list.

Passed

Test details

This test ran 4 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 174 tokens

指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 26 tokens

JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 58 tokens

标签结构复述

按官方接口的标准调用，看返回是否规范。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 93 tokens

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。有几次没对上。

Failed

Test details

This test ran 1 times: 1 failed.

品牌边界

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

用量数据是否完整

核对它报回来的用量和缓存计费。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

逻辑网格推理

用几道题看它的回答水平像不像官方模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

OpenAI 身份与安全边界

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

OpenAI 身份与安全边界

用几道题看它的回答水平像不像官方模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

按官方接口标准调用：OpenAI Responses

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

边打字边回和一次性回，结果一样吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

让它调用工具，返回格式对不对

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

让它按指定格式输出，格式兑现了吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。检测过程中确认服务类故障，剩余样本和后续检测项已熔断跳过。

Failed

Test details

This test ran 1 times: 1 failed.

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 20.7K tokens

64K 上下文能力实测

64K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 41.3K tokens

100K 上下文能力实测

100K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 63.6K tokens

200K 上下文能力实测

200K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 127.2K tokens

400K 上下文能力实测

400K 长度的内容没能稳定读完，这次就记到这里为止。

Failed

Test details

This test ran 1 times: 1 failed.
Why it failed: API authentication or permission error
Content length used: 400K

Reviews

还没有人评论，来写第一条。

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is gpt-5.6-sol genuine? Deep check result

Report ID:MZZR2026081704391656FE78Generated at：2026/08/17 12:39

Provider details AI model details

A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。

Model consistency score

Matched

gpt-5.6-sol 本次深度验真结果：Matched（86/100）。主要问题：这家接口当时太忙；有检测项没Passed。

Tested byMozhenzhen

Tested modelGPT-5.6 Sol

Providersleyanshi.me

Requests16

Duration1 min

Identity verdictVerified

ReferenceCPA 官方产品源

This call did not complete

Reason for failure

The provider was busy and could not process the request.

What to do

Try again later. Contact the provider if this persists.

Token usage check

Reported usage is used; estimates appear only when none is reported.

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 1 request

Share billed at the cache rate--

No usage record

This provider's endpoint does not report usage reliably; check it against your bill.

Usage this run0Cached tokens0Non-cached tokens0Average per run0

Usage reportedNot reportedCache billingDid not happenResultHigh risk

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.

5 tiers

Verified up to 200K

400K Failed，原因：接口鉴权或权限异常。

Current guidance

The 400K tier did not return reliably this time; do not rely on this length.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched86/100

主要问题：这家接口当时太忙；有检测项没Passed。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly8 / 12

这家接口当时太忙（隐藏提示词边界） -4

Is it the model it claims to be18 / 18

No deductions

Does it answer like the official model25 / 25

No deductions

Is usage and billing reasonable10 / 10

No deductions

Will it keep working15 / 25

这家接口当时太忙（隐藏提示词边界） -8有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed

26 checks

Model list visibility

gpt-5.6-sol is visible in the API model list.

Passed

Test details

This test ran 4 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 174 tokens

指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 26 tokens

JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 58 tokens

标签结构复述

按官方接口的标准调用，看返回是否规范。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 93 tokens

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。有几次没对上。

Failed

Test details

This test ran 1 times: 1 failed.

品牌边界

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

用量数据是否完整

核对它报回来的用量和缓存计费。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

逻辑网格推理

用几道题看它的回答水平像不像官方模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

OpenAI 身份与安全边界

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

OpenAI 身份与安全边界

用几道题看它的回答水平像不像官方模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

按官方接口标准调用：OpenAI Responses

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

边打字边回和一次性回，结果一样吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

让它调用工具，返回格式对不对

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

让它按指定格式输出，格式兑现了吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。前序检测已确认这家接口当时太忙，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。检测过程中确认服务类故障，剩余样本和后续检测项已熔断跳过。

Failed

Test details

This test ran 1 times: 1 failed.

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 20.7K tokens

64K 上下文能力实测

64K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 41.3K tokens

100K 上下文能力实测

100K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 63.6K tokens

200K 上下文能力实测

200K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 127.2K tokens

400K 上下文能力实测

400K 长度的内容没能稳定读完，这次就记到这里为止。

Failed

Test details

This test ran 1 times: 1 failed.
Why it failed: API authentication or permission error
Content length used: 400K

Reviews

还没有人评论，来写第一条。