docs: add API cost warning when making Space public#677
Open
octo-patch wants to merge 1 commit into
Open
Conversation
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.
Fixes #604
Problem
When students set their duplicated Space to public, every visitor triggers inference API calls authenticated with the Space owner's token. If the token is linked to a paid HF Inference tier or an external paid API (e.g., OpenAI), this can silently accumulate significant costs for the student.
There is currently no warning about this risk in the tutorial steps where the secret token is configured.
Solution
Added a visible blockquote warning immediately after the "Save" step in
units/en/unit1/tutorial.mdx, advising students to:Testing
Documentation-only change; no code logic affected.