What problem does it solve?
Adding a new AI provider to a self-hosted chat/app often stalls on scattered requirements—usage docs, environment variables, Docker configuration, and image assets—creating inconsistent onboarding and deployment issues.
Core Features & Use Cases
- Bilingual provider documentation: Create complete usage docs in English and Chinese, including real registration and dashboard URL references plus pricing callouts (without exposing secrets).
- Environment-variable documentation: Define provider-specific API key and model list variables with clear types, descriptions, and example formats.
- Deployment configuration updates: Update Dockerfiles (end of ENV section) and refresh .env.example so the new provider can be configured safely and consistently.
- Image resource preparation: Produce and upload the required cover and screenshot set for provider listing and LobeHub configuration.
Quick Start
Ask your team to run the full provider documentation checklist for a chosen provider-name, ensuring EN+CN docs, environment variables docs, all three Dockerfiles, .env.example, and required images are updated without including any real API keys.