llm-provider-auth

You can use your existing LLM subscriptions for API access by implementing provider-specific OAuth flows. This approach bypasses direct API key management, allowing you to authenticate via subscription tokens using PKCE and device flow mechanisms.

The PKCE OAuth flow is a secure authentication mechanism used to obtain subscription-based access tokens without exposing API keys. You need it when implementing interactive authentication for providers like OpenAI Codex or Claude, ensuring secure token exchange.

Yes, this guide covers authentication flows and API endpoints for multiple providers including GitHub Copilot and Gemini CLI. It details the specific headers, API call formats, and device flow mechanisms required to access these services using active subscriptions.

Token renewal for subscription-based LLM API calls is managed through provider-specific token refresh mechanisms detailed in the guide. You implement automated renewal processes to maintain continuous access using the refreshed subscription tokens.

Using subscription tokens instead of API keys ties your access to the terms and rate limits of your active provider subscription. This approach requires implementing specific OAuth device flows and managing token expiration for each provider, rather than using static API keys.