Skip to content

docs: clarify where to find and understand the model tier breakdown - #65

Open
Nils-Fedrigo wants to merge 2 commits into
mainfrom
docs/model-tier-breakdown
Open

docs: clarify where to find and understand the model tier breakdown#65
Nils-Fedrigo wants to merge 2 commits into
mainfrom
docs/model-tier-breakdown

Conversation

@Nils-Fedrigo

@Nils-Fedrigo Nils-Fedrigo commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Document how model access tiers map models and reasoning efforts, and where admins can inspect the current breakdown in the product.

Changes

  • Added a current model-by-model and reasoning-effort-by-reasoning-effort breakdown for Cost efficient, Balanced, and Premium tiers.
  • Added a note that the table reflects the catalog as of August 12, 2026, and that the Usage page remains the source of truth as model availability changes.
  • Documented how to open the tier breakdown from Admin > Usage.
  • Listed the exact locations of the info icon in the Members, Groups, and Settings tabs.
  • Updated the related FAQ answer to link to the new section.

Testing

  • Ran git diff --check locally.
  • Verified the table against the current model-tier explainer and static tier assignments in dust-tt/dust main at commit 492701a39082651b41630e3e1fcabcb8365e1152.
  • No full docs build was run in the Computer. Final validation is expected through PR CI.

@mintlify

mintlify Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Dust 🟢 Ready View Preview Aug 12, 2026, 10:13 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@LeandreLeBizec LeandreLeBizec changed the title docs: clarify where to find the model tier breakdown docs: clarify where to find and understand the model tier breakdown Aug 12, 2026
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