Skip to content

docs(unit1): warn about API cost risk when sharing a public Space - #741

Open
ammar-iitm wants to merge 1 commit into
huggingface:mainfrom
ammar-iitm:docs/clarify-secret-cost-risk-unit1-tutorial
Open

ammar-iitm wants to merge 1 commit into
huggingface:mainfrom
ammar-iitm:docs/clarify-secret-cost-risk-unit1-tutorial

Conversation

@ammar-iitm

Copy link
Copy Markdown

Summary

Fixes #604.

In Unit 1's "Let's Create Our First Agent Using smolagents" tutorial, learners add their Hugging Face token as an HF_TOKEN secret to their duplicated Space. If that Space is made public, every visitor's use of the demo triggers API calls authenticated with the owner's token — which can unexpectedly rack up costs for the owner if the token is tied to a paid Inference Provider or paid plan. This wasn't called out anywhere near the secret-setup steps.

Changes

  • Added a warning note right after the HF_TOKEN secret setup steps in units/en/unit1/tutorial.mdx, explaining that a public Space's API usage is billed to the owner's token and to keep an eye on usage if on a paid plan.

Testing

Documentation-only change (English unit1 content). No code/tests affected.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BRoX7i7x45LeTw8EWuvY1L

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.

[UPDATE] Clarify API Cost Risks when using Secrets in Public Hugging Face Spaces (Unit 1)

1 participant