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。
Identity confirmedModel verified
Confirmed as the official kimi-k3
Behavior matches the official kimi-k3.
Brand consistency96/100
Model match score (kimi-k3)96/100
Checks15/16 Passed
- Providers
- a6api
- Claimed model
- kimi-k3
- Plan
- Full check
- Reference
- 103 official models
- Requests
- 13
- Duration
- 23 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference103 official models · 3/3 Valid
Answer by answer3 answers: 3 match kimi-k3
Similarity to official modelsTop 5
- kimi-k3Claimed model96%
- claude-opus-52%
- doubao-seed-2-1-pro<1%
- mimo-v2.6-flash<1%
- claude-opus-5-5<1%
02Test details
16 items · 15 passed · 1 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 kimi-k3 |
| 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 Moonshot Kimi family; brand match score 96 |
| C-03 | Model consistency | Match | 与官方 kimi-k3 吻合，型号一致度 96 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口没有返回结果，本项未完成。 |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M 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 | Supported | Returned in the required JSON structure |
03Which apps can connect
Tried once per app with kimi-k3, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
接口没有返回结果，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 400K
Read in full up to 400K; 1M failed: The endpoint returned no result.
Reference windowVerified up to 400KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 27.1K received
- 128KRead in full · 121.7K received
- 400KRead in full · 376.0K received
- 1MThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage535.1KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation58% 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.
Reviews
还没有人评论，来写第一条。
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
kimi-k3 verification report
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。
Identity confirmedModel verified
Confirmed as the official kimi-k3
Behavior matches the official kimi-k3.
Brand consistency96/100
Model match score (kimi-k3)96/100
Checks15/16 Passed
- Providers
- a6api
- Claimed model
- kimi-k3
- Plan
- Full check
- Reference
- 103 official models
- Requests
- 13
- Duration
- 23 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference103 official models · 3/3 Valid
Answer by answer3 answers: 3 match kimi-k3
Similarity to official modelsTop 5
- kimi-k3Claimed model96%
- claude-opus-52%
- doubao-seed-2-1-pro<1%
- mimo-v2.6-flash<1%
- claude-opus-5-5<1%
02Test details
16 items · 15 passed · 1 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 kimi-k3 |
| 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 Moonshot Kimi family; brand match score 96 |
| C-03 | Model consistency | Match | 与官方 kimi-k3 吻合，型号一致度 96 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口没有返回结果，本项未完成。 |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M 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 | Supported | Returned in the required JSON structure |
03Which apps can connect
Tried once per app with kimi-k3, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
接口没有返回结果，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 400K
Read in full up to 400K; 1M failed: The endpoint returned no result.
Reference windowVerified up to 400KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 27.1K received
- 128KRead in full · 121.7K received
- 400KRead in full · 376.0K received
- 1MThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage535.1KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation58% 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.
Reviews
还没有人评论，来写第一条。
发表评论