API key authentication

[khadni]

This pull request updates the CRE documentation to clarify authentication methods for the CLI, introducing API key authentication as an alternative to browser-based login. The changes improve guidance for CI/CD and headless environments, detail how to use API keys, and update all relevant guides and reference material to reflect the new authentication options and requirements.

Authentication method updates:

• Added documentation and guidance for API key authentication, including usage instructions, environment variable setup (CRE_API_KEY), and security cautions. This enables non-interactive authentication for CI/CD and headless environments. [1] [2] [3]
• Updated all authentication-related guides and references to distinguish between browser-based login (cre login) and API key authentication, including requirements for Early Access approval. [1] [2] [3] [4]

Workflow deployment requirements:

• Revised workflow deployment guides to require "authenticated" status (via either login or API key), replacing previous "logged in" language, and clarified verification steps. [1] [2] [3]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview	Feb 15, 2026 0:22am

[github-actions]

👋 khadni, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!