Identity confirmedModel verified
Confirmed as the official claude-fable-5-1
行为特征与官方 claude-fable-5-1 吻合；与同代近似型号 claude-fable-5 几乎相同，均高度符合。
Brand consistency99/100
Model match score (含同代近似型号 claude-fable-5)99/100
Checks15/17 Passed
- Providers
- leyanshi.me
- Claimed model
- claude-fable-5-1
- Plan
- Full check
- Reference
- 94 official models
- Requests
- 14
- Duration
- 11 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference94 official models · 3/3 Valid
Similarity to official modelsTop 5
- claude-fable-5-1 · claude-fable-5Claimed model and its near-identical sibling — both match closely99%
- kimi-k3<1%
- gpt-5.4-mini<1%
- claude-sonnet-5<1%
02Test details
17 items · 15 passed · 2 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes claude-fable-5-1 |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the Anthropic Claude family; brand match score 99 |
| C-03 | Model consistency | Match | 与官方 claude-fable-5-1 吻合；与同代近似型号 claude-fable-5 几乎相同 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 90% of repeated requests were billed at the cache price. |
| D-02 | Context length | 32K failed | 32K failed: The endpoint returned no result. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio90.1%
Cache billing works
On average 90% of repeated requests were billed at the cache price.
Usage this run50.1KCached tokens36.1KNon-cached tokens14.0KAverage per run10.0K
Usage reportedReportedCache billingHappenedResultCache billing works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: The endpoint returned no result.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32KThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage57.3KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation96% 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.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Post an anonymous comment
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
claude-fable-5-1 verification report
Identity confirmedModel verified
Confirmed as the official claude-fable-5-1
行为特征与官方 claude-fable-5-1 吻合；与同代近似型号 claude-fable-5 几乎相同，均高度符合。
Brand consistency99/100
Model match score (含同代近似型号 claude-fable-5)99/100
Checks15/17 Passed
- Providers
- leyanshi.me
- Claimed model
- claude-fable-5-1
- Plan
- Full check
- Reference
- 94 official models
- Requests
- 14
- Duration
- 11 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference94 official models · 3/3 Valid
Similarity to official modelsTop 5
- claude-fable-5-1 · claude-fable-5Claimed model and its near-identical sibling — both match closely99%
- kimi-k3<1%
- gpt-5.4-mini<1%
- claude-sonnet-5<1%
02Test details
17 items · 15 passed · 2 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes claude-fable-5-1 |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the Anthropic Claude family; brand match score 99 |
| C-03 | Model consistency | Match | 与官方 claude-fable-5-1 吻合；与同代近似型号 claude-fable-5 几乎相同 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 90% of repeated requests were billed at the cache price. |
| D-02 | Context length | 32K failed | 32K failed: The endpoint returned no result. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio90.1%
Cache billing works
On average 90% of repeated requests were billed at the cache price.
Usage this run50.1KCached tokens36.1KNon-cached tokens14.0KAverage per run10.0K
Usage reportedReportedCache billingHappenedResultCache billing works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: The endpoint returned no result.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32KThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage57.3KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation96% 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.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.