DX-596-together-chat-completions: sync with mintlify-docs#1269 - #61
Open
zainhas wants to merge 1 commit into
Open
DX-596-together-chat-completions: sync with mintlify-docs#1269#61zainhas wants to merge 1 commit into
zainhas wants to merge 1 commit into
Conversation
Clarify that serverless rate-limit headers only appear on 429 responses, per docs/serverless/rate-limits.mdx clarification. Source: togethercomputer/mintlify-docs#1269
Broly Security ScanNote ✅ Clean scan Note Re-scan this PR anytime with
|
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.
Syncs the
together-chat-completionsskill with the rate-limit clarification landed in togethercomputer/mintlify-docs#1269 (merge commit5bde72f).Triggering doc file
docs/serverless/rate-limits.mdx— clarifies thatx-ratelimit-reset(and the otherx-ratelimit-*/x-tokenlimit-*headers) only appear on429 Too Many Requestsresponses. Successful requests come back with no rate-limit headers. The docs also reworded the intro sentence and the inspect-your-limit code sample to reflect this.Skill changes
references/api-parameters.md— Rate Limits & Build Tiers section:429responses includex-ratelimit-resetwith the number of seconds to wait before retrying.429 Too Many Requestsresponses; successful responses do not include them. Header reference:".x-ratelimit-resetrow description from "Time until the request window resets" to "Seconds to wait before retrying" to match the doc's wording.429responses and back off using thex-ratelimit-resetvalue instead of a hard-coded RPM table".quick_validate.py skills/together-chat-completionspasses.Not synced (deliberately)
docs/dedicated-endpoints/adapter.mdxanddocs/dedicated-endpoints/rollouts.mdxalso changed in mintlify-docs#1269 (SDKclient.beta.models.createsignature flattening, new "Check revision validation" section,validator-ignoremarkers on rollout snippets). These are all v2-surface content and the current-maintogether-dedicated-endpointsskill is entirely v1 (zero mentions ofbeta.models,revisions,REVISION_VALIDATION_STATUS_*,validationStatus). Same v2-surface-addition-without-landing-target pattern as mintlify-docs#1244 / #1251 — logged, no separate PR opened.docs/mixture-of-agents.mdx,docs/parallel-workflows.mdx, and thescripts/snippets/**validator changes in mintlify-docs#1269 are unmapped in.skills/sync-map.yaml, so no skill is affected.Generated by the Sync Skills Cursor Automation. Please review before merging.