Newsletter drafts

What must change before the prototype becomes public?

Treat release as a separate decision from completing the learning project. OpenAI’s official API guidance warns against putting secret keys in browser/mobile client code or committing them to a repository. Exposure can enable unauthorized requests and charges. (help.openai.com)

Its current project-management documentation also distinguishes spend alerts from enforced limits. Alerts do not stop requests; the documented hard-limit option must be enabled separately, and enforcement can lag enough for spending to exceed the configured amount slightly. (help.openai.com)

Our release checklist:

  • An adult has approved the accounts, billing owner and applicable terms.
  • No family information, confidential employer material or exposed credentials are included.
  • Access controls and spending behavior have been checked in the actual setup.
  • The mentor has demonstrated how to disable the application and revoke access.
  • The learner can describe known failures and the intended audience.
  • Publicity and portfolio permissions have been considered separately.

If these checks are unresolved, keep the demonstration private. A public URL is not our recommended condition for a successful learning outcome.

Sources cited on this page

  1. Best practices for API key safety | OpenAI Help Center ↗help.openai.com
  2. Managing projects in the API platform | OpenAI Help Center ↗help.openai.com