Open weight models 1 - #19
Merged
Merged
Conversation
📝 WalkthroughWalkthroughAdds model reference pages and dedicated authenticated OpenAPI playground specifications for ChangesModel playground documentation
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant Client
participant ChatCompletionsAPI
participant Model
Client->>ChatCompletionsAPI: POST /v1/chat/completions with x-api-key and model
ChatCompletionsAPI->>Model: Process chat completion request
Model-->>ChatCompletionsAPI: Return completion response
ChatCompletionsAPI-->>Client: Return 200 or documented error response
Possibly related PRs
Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@api-reference/models/glm-5-2.mdx`:
- Around line 4-14: Update the GLM-5.2 page’s description and model overview to
remove or qualify the claims about function calling and batch tasks unless the
linked OpenAPI playground is expanded to expose those contracts. Keep the
advertised capabilities consistent with the Chat Completions schema referenced
by the page, including its lack of tools, tool_choice, tool messages, and
tool_call_id support.
In `@api-reference/openapi/playgrounds/deepseek-v4-flash.openapi.json`:
- Line 6: Update the description in the deepseek-v4-flash playground OpenAPI
definition to match the examples declared under the request-example
configuration: either remove the claim that the selector supports JSON, NER, and
PII workflows, or add corresponding example entries alongside default.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 911d6fee-f74d-4a29-929b-d75f2567b63e
📒 Files selected for processing (4)
api-reference/models/deepseek-v4-flash.mdxapi-reference/models/glm-5-2.mdxapi-reference/openapi/playgrounds/deepseek-v4-flash.openapi.jsonapi-reference/openapi/playgrounds/glm-5_2.openapi.json
Comment on lines
+4
to
+14
| description: "Model details for glm-5.2. Reasoning, function calling, and batch tasks with a 1M-token context window." | ||
| openapi: "api-reference/openapi/playgrounds/glm-5_2.openapi.json POST /chat/completions" | ||
| --- | ||
|
|
||
| <Note> | ||
| This model supports the Chat Completions API only. Send requests to | ||
| `/v1/chat/completions` — the Responses endpoint (`/v1/responses`) is not | ||
| available for this model. | ||
| </Note> | ||
|
|
||
| > Z.ai's GLM-5.2 is an open-weight Mixture-of-Experts flagship built for long-horizon tasks, with 753B total parameters activating 8 of 256 experts per token, served on ZeroGPU for general text generation. It sustains a solid 1,048,576-token (1M) context, reasons through a problem with flexible thinking effort before answering, and supports function calling and batch tasks. MIT-licensed with no usage restrictions. When the work spans entire repos, day-long agent sessions, or million-token documents, this is the model. |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Do not advertise API capabilities this page cannot expose.
Lines 4 and 14 promise function calling and batch tasks, but the linked playground defines only Chat Completions; it also lacks tools, tool_choice, tool messages, and tool_call_id. Add the supported tool-calling/Batch API contracts, or remove/qualify these claims to avoid sending users to unsupported flows.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@api-reference/models/glm-5-2.mdx` around lines 4 - 14, Update the GLM-5.2
page’s description and model overview to remove or qualify the claims about
function calling and batch tasks unless the linked OpenAPI playground is
expanded to expose those contracts. Keep the advertised capabilities consistent
with the Chat Completions schema referenced by the page, including its lack of
tools, tool_choice, tool messages, and tool_call_id support.
| "info": { | ||
| "title": "deepseek-v4-flash playground", | ||
| "version": "1.0", | ||
| "description": "Interactive playground for **deepseek-v4-flash**.\nModel is always `deepseek-v4-flash` on this page (shown in the form, not editable).\nUse the **request example** selector to switch use cases (JSON, NER, PII, etc.).\nAuthentication: `x-api-key` (required) and `x-project-id` (optional)." |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Make the request-example guidance match the available examples.
Lines 61-79 define only default, so the selector cannot offer the advertised JSON, NER, or PII workflows. Remove that claim or add the corresponding examples.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@api-reference/openapi/playgrounds/deepseek-v4-flash.openapi.json` at line 6,
Update the description in the deepseek-v4-flash playground OpenAPI definition to
match the examples declared under the request-example configuration: either
remove the claim that the selector supports JSON, NER, and PII workflows, or add
corresponding example entries alongside default.
This was referenced Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
/v1/chat/completions; the Responses endpoint is unavailable.