Fill gaps from assistant conversations: pricing model and reasoning discovery - #418
Open
mintlify[bot] wants to merge 2 commits into
Open
Fill gaps from assistant conversations: pricing model and reasoning discovery#418mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Address recurring assistant confusion about how the API is billed relative to consumer plans, and clarify that reasoning support extends beyond the models listed in the effort tables.
Changes
overview/pricing.mdx: added a "How the API bills" section explaining pay-as-you-go metering, no free tier, and that Free/Pro/Max plans on venice.ai apps do not grant API allowances. Aligns the English page with the intro already present in the localized (zh/ko/es/fr/de/pt-BR/it/ar) versions.overview/pricing.mdx: expanded the "Pro Users" section to state that the one-time $10 credit is the only Pro benefit on the API, that no recurring API allowance is included, and that Pro-only models returnAUTHENTICATION_FAILED_INACTIVE_KEYwhen called without an active Pro subscription.guides/features/reasoning-models.mdx: added a note above the model-support tables that other models may still emit reasoning tokens (visible inusage.completion_tokens_details.reasoning_tokens) even when not listed, and to checksupportsReasoning/supportsReasoningEfforton/v1/modelsfor authoritative capability discovery.Context
Recurring assistant conversations showed users confused about whether Pro subscription allowances apply to API usage (multiple pricing-bucket threads) and unsure how to tell if a specific model is a reasoning model when it is not called out in the reasoning-models page.