Skip to content

DX-596-together-chat-completions: sync with mintlify-docs#1269 - #61

Open
zainhas wants to merge 1 commit into
mainfrom
docs-sync/together-chat-completions/mintlify-docs-pr-1269
Open

DX-596-together-chat-completions: sync with mintlify-docs#1269#61
zainhas wants to merge 1 commit into
mainfrom
docs-sync/together-chat-completions/mintlify-docs-pr-1269

Conversation

@zainhas

@zainhas zainhas commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Syncs the together-chat-completions skill with the rate-limit clarification landed in togethercomputer/mintlify-docs#1269 (merge commit 5bde72f).

Triggering doc file

  • docs/serverless/rate-limits.mdx — clarifies that x-ratelimit-reset (and the other x-ratelimit-* / x-tokenlimit-* headers) only appear on 429 Too Many Requests responses. 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:
    • Rewrite the intro sentence: successful responses do not include rate-limit headers; 429 responses include x-ratelimit-reset with the number of seconds to wait before retrying.
    • Retitle the header table intro to "Rate-limit headers only appear on 429 Too Many Requests responses; successful responses do not include them. Header reference:".
    • Update the x-ratelimit-reset row description from "Time until the request window resets" to "Seconds to wait before retrying" to match the doc's wording.
    • Rewrite the misleading "plan against the latest headers instead of a hard-coded RPM table" best-practice bullet to "watch for 429 responses and back off using the x-ratelimit-reset value instead of a hard-coded RPM table".

quick_validate.py skills/together-chat-completions passes.

Not synced (deliberately)

  • docs/dedicated-endpoints/adapter.mdx and docs/dedicated-endpoints/rollouts.mdx also changed in mintlify-docs#1269 (SDK client.beta.models.create signature flattening, new "Check revision validation" section, validator-ignore markers on rollout snippets). These are all v2-surface content and the current-main together-dedicated-endpoints skill is entirely v1 (zero mentions of beta.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 the scripts/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.

Clarify that serverless rate-limit headers only appear on 429 responses,
per docs/serverless/rate-limits.mdx clarification.

Source: togethercomputer/mintlify-docs#1269
@broly-code-security-scanner

Copy link
Copy Markdown

Broly Security Scan

Note

Clean scan
No vulnerabilities detected in this PR.

Note

Re-scan this PR anytime with /broly scan — useful after /broly undismiss, or to refresh findings without a new push.

Broly — SAST (zai-org/GLM-5.2) · Secrets · SCA · GH Actions (zizmor) · Containers · SBOM · Powered by Together AI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants