Is deepseek-v4-flash-vision-exp genuine? Standard check result
Doubtful
deepseek-v4-flash-vision-exp 本次标准验真结果:Doubtful(61/100)。主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
deepseek-v4-flash-vision-exp 本次标准验真结果:Doubtful(61/100)。主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
Reported usage is used; estimates appear only when none is reported.
Review API availability, model identity, response completeness, and other checks separately.
主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
Expand any row for details; anything private has been removed.
deepseek-v4-flash-vision-exp is visible in the API model list.
This test ran 7 times; result: Passed.
The basic API call succeeded and returned a recognizable response.
This test ran 1 times; result: Passed.
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Self-reported model identity needs review
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 133 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 116 tokens
按官方接口的标准调用,看返回是否规范。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Tag-structure repetition was unstable
用几道题看它的回答水平像不像官方模型。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Hidden-prompt boundary was unclear This test used 400 tokens
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Brand-boundary response was unclear
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 403 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 448 tokens
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Model-code anchoring was unstable This test used 400 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 180 tokens
对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 5 次都对。
This test ran 5 times: 5 passed. This test used 13.9K tokens of which 13.1K tokens were billed at the cache price
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhendeepseek-v4-flash-vision-exp 本次标准验真结果:Doubtful(61/100)。主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
Reported usage is used; estimates appear only when none is reported.
Review API availability, model identity, response completeness, and other checks separately.
主要问题:问它是哪个型号时答案会变;问到不该说的内容时把握不住分寸;让它原样复述结构时会出错。
Expand any row for details; anything private has been removed
deepseek-v4-flash-vision-exp is visible in the API model list.
This test ran 7 times; result: Passed.
The basic API call succeeded and returned a recognizable response.
This test ran 1 times; result: Passed.
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Self-reported model identity needs review
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 133 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 116 tokens
按官方接口的标准调用,看返回是否规范。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Tag-structure repetition was unstable
用几道题看它的回答水平像不像官方模型。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Hidden-prompt boundary was unclear This test used 400 tokens
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Brand-boundary response was unclear
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 403 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 448 tokens
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Model-code anchoring was unstable This test used 400 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 180 tokens
对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 5 次都对。
This test ran 5 times: 5 passed. This test used 13.9K tokens of which 13.1K tokens were billed at the cache price
还没有人评论,来写第一条。
发表评论