docs: document Atlas Cloud as a custom OpenAI-compatible LLM provider#332
Open
lucaszhu-hue wants to merge 1 commit into
Open
docs: document Atlas Cloud as a custom OpenAI-compatible LLM provider#332lucaszhu-hue wants to merge 1 commit into
lucaszhu-hue wants to merge 1 commit into
Conversation
Atlas Cloud exposes an OpenAI-compatible API, so it works with PentAGI's existing LLM_SERVER_* custom-provider variables with no code changes. Add an "Atlas Cloud (OpenAI-compatible)" subsection to the Custom LLM Provider Configuration section and a commented example to .env.example. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lucaszhu-hue
force-pushed
the
docs/atlascloud-custom-provider
branch
from
863d355 to
91f9e0c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the Change
Problem
PentAGI supports many LLM providers, including a generic Custom (
LLM_SERVER_*) OpenAI-compatible endpoint, but the docs don't mention Atlas Cloud — a full-modal inference platform that serves the DeepSeek / Qwen / GLM / Kimi / MiniMax models PentAGI already targets, through one OpenAI-compatible API.Solution
Document Atlas Cloud as a custom OpenAI-compatible provider. No code change — it uses the existing
LLM_SERVER_*variables:README.md: an "Atlas Cloud (OpenAI-compatible)" subsection under Custom LLM Provider Configuration, with a config example, a reasoning-model note, and a collapsed list of all available Atlas chat models..env.example: a commented Atlas Cloud example in the Custom LLM provider block.N/A (no related issue)
Type of Change
Areas Affected
Testing and Verification
Test Configuration
Test Steps
LLM_SERVER_URL=https://api.atlascloud.ai/v1,LLM_SERVER_KEY=<key>,LLM_SERVER_MODEL=deepseek-ai/deepseek-v4-pro,LLM_SERVER_PROVIDER=openai.Test Results
Verified the documented endpoint directly: a non-streaming
POST /v1/chat/completionsto Atlas withdeepseek-ai/deepseek-v4-proreturns HTTP 200 with a valid completion. Docs/config only — no Go/TypeScript paths changed, sogo vet/pnpm lintare unaffected.Documentation Updates
Checklist
Code Quality
Security
Compatibility
Additional Notes
This README lists providers as text (no provider logos), so I kept the Atlas entry text + link to match the existing style. Happy to adjust wording or placement.
🤖 Generated with Claude Code