Repository navigation
fix: resolve duplicate CreateMessageRequest schema and YAML indentation errors - #166
Merged
Merged
Conversation
…on errors The Anthropic Messages API schema added in #165 reused the name CreateMessageRequest, which already exists for the Assistants API. The duplicate mapping key breaks strict YAML parsing and fails mint validate in docs. Rename the Anthropic schema to CreateAnthropicMessageRequest and update its references. Also indent four closing flow-sequence brackets in guardrail examples that strict parsers reject with 'deficient indentation'.
There was a problem hiding this comment.
🟢 Approval recommended
The targeted schema rename and indentation fixes are consistent, with no unresolved review findings.
No open issues 🎉
What changed in this PR
This PR removes a schema-name collision between the Anthropic Messages and Assistants APIs and fixes YAML indentation that blocked strict parsing and documentation validation.
Changes:
- Renames the Anthropic request schema to
CreateAnthropicMessageRequestand updates the/messagesreference, preserving the Assistants schema name. - Updates the schema name mentioned in the token-count request description.
- Corrects closing-bracket indentation in four guardrail examples without changing their values.
| File | Description |
|---|---|
openapi.yaml |
Separates the request schema names and corrects guardrail example indentation. |
Review effort: Balanced
sk-portkey
approved these changes
Oct 22, 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
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.
Problem
mint validatein docs-core fails against the currentmasterspec:#165 added the Anthropic Messages API schema as
CreateMessageRequest, but that name is already used by the Assistants API (/threads/{thread_id}/messages,additional_messages, thread creation).Strict YAML parsers (js-yaml, Redocly) also reject four guardrail examples with
deficient indentation: the closing]of a multi-line flow sequence was at the same indentation as its key.Changes
CreateAnthropicMessageRequestand updated its$refonPOST /messagesplus the mention inCountMessageTokensRequest. The Assistants API schema keeps the original name.]brackets (whitespace only).Verification
npx js-yaml openapi.yamlparses cleanly.mint validatein docs-core passes against this spec (build validation passed).