API key, session, scope, and playground authentication notes.
Developer authentication docs explain how API examples relate to a reader's Brothh session, publishable key, future secret key, and playground access. This page should be the first stop before any API endpoint that requires account context.
Secret-key issuance is still gated. Do not document a live secret-key reveal flow until the schema/API path exists. If an example needs a secret, use a clearly marked placeholder such as `sk_test_demo_xxx` and state that live secrets are not shown in GitBook yet.
If a reader is signed out, route them to `/auth/login?next=/developers/auth`. If the viewer context cannot load, keep the page readable and show placeholders rather than failing the article render.